Gary Huff
My feedback
-
15 votesGary Huff
supported this idea
·
-
46 votes
An error occurred while saving the comment 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
·
-
1,602 votesUnder Review ·
AdminPatrick Palmer
(Director of Product Management, Pro Video and Motion Design, Adobe DVA)
responded
Thanks for all the feedback. It’s pretty clear that we’ve got to look into the workflow using this format more closely, there are enough reports about gaps at this point to reopen this item. I’ll post more info about next steps shortly. In the meantime, a couple of questions are easy to answer:
- The plugin is designed for Premiere Pro. It currently doesn’t provide support for After Effects.
- It does work with AME, so if you want to use it for batch processing, that’s very doable
- If you’ve started a project with Autokroma, there’s no easy way to transfer it to be running with the new plugin.Patrick
Gary Huff
supported this idea
·
-
3 votes
An error occurred while saving the comment Gary Huff
commented
I just made ProRes proxies via Resolve. Exact same filename (no _proxy or _P like the C300 Mark III generated proxies), only the extension is different (CRM for originals, and MOV for the ProRes).
Premiere cannot link all the proxies automatically just because the extension does not match even though I have unchecked "File Extension". I have hundreds of clips to link proxies to, this is madness.
An error occurred while saving the comment Gary Huff
commented
This issue is still ongoing as of 22.3 released today.
An error occurred while saving the comment Gary Huff
commented
This issue persists with the latest Premiere update (22.2)
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
·
-
3 votesGary Huff
shared this idea
·
-
18 votesGary Huff
supported this idea
·
-
5 votes
An error occurred while saving the comment Gary Huff
commented
This issue is still ongoing with the latest Premiere update (22.2).
An error occurred while saving the comment Gary Huff
commented
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.
Gary Huff
supported this idea
·
-
Bug: Using Export Frame on clips with proxies (even if proxies not toggled), results in low res JPGs
29 votesAn error occurred while saving the comment Gary Huff
commented
The new Premiere 22.2 update seems to have fixed this issue.
An error occurred while saving the comment Gary Huff
commented
This is also a problem if you have Rec.709 proxies and Log master footage. If I want to export a still to showcase, say, a temporary color grade, it applies the effect to the Rec.709 proxy footage and exports that, even if I have proxies turned off in the viewer.
Gary Huff
supported this idea
·
-
3 votes
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
·
-
124 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
·
-
92 votesGary Huff
supported this idea
·
-
Need captions in V 15 and above to travel till the bottom of the screen irrespective of safe margins
20 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
·
-
269 votesGary Huff
supported this idea
·
-
3 votesGary Huff
shared this idea
·
-
61 votesGary Huff
supported this idea
·
-
77 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
·
-
15 votesGary Huff
supported this idea
·
-
12 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
·
This bug is still ongoing in 22.3.0 involving the use of XF-AVC clips that have custom filenames. Clips ending in _CANON.MXF are fine, but anything else causes them to be imported as CLIPS001.