Gary Huff
My feedback
-
5 votes
An error occurred while saving the comment Gary Huff
supported this idea
·
-
2 votes
An error occurred while saving the comment Gary Huff
commented
Can confirm that this is an issue. Trying to attach proxies with recorded proxies in a C300 Mark III or a C70. With the previous version of Premiere, I could have "File Extension" and "Media Start" checked and it would attach the proxies to every clip, but with Premiere v22.0.0 it will only do one clip at a time.
Gary Huff
supported this idea
·
-
1 vote
An error occurred while saving the comment Gary Huff
commented
It seems to be the AVCHD footage. I used EditReady to re-wrap the clips because I was getting incredibly poor performance with the previous version of Premiere (the one right before v20.0), but the rewrap made things better. Now I am having this issue, but I transcoded the re-wrapped AVCHD clip to ProRes Proxy and that has appeared to fix the issue for now.
Gary Huff
shared this idea
·
-
95 votes
This is by design. We always keep captions within safe margins (10%). Would an option to defeat this restriction be useful or is it better to remove this safeguard all together. Opinions welcome.
Gary Huff
supported this idea
·
-
1 voteGary Huff
shared this idea
·
-
87 votesGary Huff
supported this idea
·
-
Need captions in V 15 and above to travel till the bottom of the screen irrespective of safe margins
18 votesAn error occurred while saving the comment Gary Huff
commented
I work primarily in subtitles and not captions, but currently with the revamped workflow for captions, I am so far unable to place subtitles below the title safe area. I can select the bottom middle zone, but I can only offset its normal placement upward in the frame, not downward. For content that won't normally be seen on a normal TV screen, I would prefer to have the subtitles placed at the bottom of the screen, below title safe. Under the old process, I could achieve this with the Effects tab, but now those properties do not seem to be accessible for the new captions track.
Gary Huff
supported this idea
·
-
234 votesGary Huff
supported this idea
·
-
3 votesGary Huff
shared this idea
·
-
57 votesGary Huff
supported this idea
·
-
74 votes
An error occurred while saving the comment Gary Huff
commented
I do not know why this doesn't have more votes. I like to label my clips to differentiate by speaker, but what we need are just the color swatches, not even the names, and, even better, custom text for each color so I know what the colors refer to as reference when coming back to a project.
Gary Huff
supported this idea
·
-
14 votesGary Huff
supported this idea
·
-
42 votes
An error occurred while saving the comment Gary Huff
commented
This issue is currently resolved unless the "User Defined" field is altered from "CANON" to something else. So a clip with a filename of "A001C059_20012242_CANON.mxf" will import just fine, but a clip named "A001C001_200527XT_AYRO0.mxf" (using the User Defined option in the camera) will import as CLIPS001. Renaming the files to remove the custom field allow them to import with proper file names.
An error occurred while saving the comment Gary Huff
commented
Just tested it with 14.0.1 and XF-AVC clips imported through Media Browser or drag-and-dropped right into the project bin are named "CLIPS001", every one of them. This is on macOS Mojave 2017 iMac.
An error occurred while saving the comment Gary Huff
commented
Just tried importing the clips directly and it does the same thing, they are all named "CLIPS001".
Gary Huff
shared this idea
·
-
11 votesGary Huff
supported this idea
·
-
5 votes
An error occurred while saving the comment Gary Huff
commented
I have tried this and it does not work very well, probably because the auto ducking feature isn't tuned enough for two people on separate mics.
Gary Huff
supported this idea
·
-
2 votes
An error occurred while saving the comment Gary Huff
commented
This is no longer just in scrubbing, I have now had a corrupted timeline due to this issue.
Gary Huff
shared this idea
·
-
385 votesGary Huff
supported this idea
·
-
84 votes
An error occurred while saving the comment Gary Huff
commented
I just had this issue happen on Premiere Pro 2020 (14.0.0) as well (same machine, a maxed out 2017 iMac).
An error occurred while saving the comment Gary Huff
commented
This happens to me as well, Premiere 13.1.4 on Mojave 10.14.6. I can change the GPU from OpenCL to Metal and then back and this fixes the issue.
Gary Huff
supported this idea
·
-
3 votesGary Huff
shared this idea
·
-
41 votesGary Huff
supported this idea
·
I have encountered this with proxies that have different names than the original clips (such as the C300 series which appends a _P to the end of the filenames to differentiate the proxies). With the previous Premiere, in v21, I could tell to to match the proxies via the File Extension and Media Start, and it would attach proxies to all the clips perfectly. This behavior no long happens in v22 of Premiere. I have done some other pre-created proxies which have the exact same name, and that seems to work with multiple clips, but so far that situation has involved 2 clips, not hundreds like the ones that are not working with the C300 generated proxies.