Gary Huff
My feedback
-
20 votes
An error occurred while saving the comment Gary Huff
supported this idea
·
-
4 votes
An error occurred while saving the comment Gary Huff
commented
2020 here with 14.3.1, this is still happening.
Gary Huff
supported this idea
·
-
17 votes
An error occurred while saving the comment Gary Huff
commented
This is still a problem for me with 14.3.1 in 2020.
Gary Huff
supported this idea
·
-
113 votesGary Huff
supported this idea
·
-
3 votesGary Huff
shared this idea
·
-
49 votesGary Huff
supported this idea
·
-
70 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
·
-
38 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
·
-
10 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
·
-
361 votesGary Huff
supported this idea
·
-
58 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
·
-
28 votesGary Huff
supported this idea
·
-
2 votesGary Huff
shared this idea
·
-
296 votes
Thank you for your feedback. This is under review.
Gary Huff
supported this idea
·
-
4 votesGary Huff
shared this idea
·
-
14 votes
An error occurred while saving the comment Gary Huff
commented
To add to this, Composite Preview During Trim ignores the setting if you use keyboard commands to do the trim on my machine. I have it toggled off because it's laggy, but if I use the keyboard commands to trim (i.e. Alt + Left or Right Arrow in Ripple Edit) it goes into Composite Preview. This needs to be fixed ASAP.
Gary Huff
supported this idea
·
14.3.1 still has this bug, I cannot get imported SRT files that I lay on a video track to export out via Media Encoder even though they render just fine if done straight out of Premiere.