Joel Ferland
My feedback
-
583 votesUnder Review ·
AdminPatrick Palmer
(Director of Product Management, Pro Video and Motion Design, Adobe DVA)
responded
All,
first of all I wanted to thank everyone for making this a productive conversation over the last couple of days.
As several people responded to my comment about keeping the tone civilised, I need to dwell on that for a minute. Please hear me out, this is important to everyone on my crew and I hope it will be to you.
Saying that we shouldn't be surprised when things get heated is very problematic in my opinion. How do you expect a junior person on my team to respond to a technical question when it is combined with something that can easily be described as hate speech? How do you think we can actually come together on actual issues when there's already the assumption that we're a big faceless corporation, not even listening to our customers?
People on my team have received threats. I've been there over the years,…
Joel Ferland
supported this idea
·
-
132 votesIn Progress · 62 comments · Premiere Pro » Preference & Settings · Flag idea as inappropriate… · Admin →Joel Ferland
supported this idea
·
-
2 votesJoel Ferland
shared this idea
·
-
125 votesJoel Ferland
supported this idea
·
-
8 votes
An error occurred while saving the comment Joel Ferland
shared this idea
·
-
10 votesJoel Ferland
supported this idea
·
-
15 votesJoel Ferland
supported this idea
·
-
20 votes
An error occurred while saving the comment Joel Ferland
commented
Same here in Premiere 2021 (v15.2) : it seems to work when exporting in the same codec as the timeline, however, if I export a rendered ProRes timeline with loads of effects in MP4, Premiere don't use the previews to convert to MP4, instead it all re-renders the effects to export to MP4. Very annoying and it wasn't the case in Premiere 2020
Joel Ferland
supported this idea
·
-
2 votes
An error occurred while saving the comment Joel Ferland
commented
Still present in version 15.2 (Premiere Pro 2021)
An error occurred while saving the comment Joel Ferland
commented
Tested again today with Beta 15.1.0 build 10.
608 captions are still OK
708 captions are no longer always in "Paint On" mode, but again they appear about 6 frames later in the exported MXFAn error occurred while saving the comment Joel Ferland
commented
Hi, I had a chance to test it and the timecode (in Premiere and also on exported files) are correct.
When testing, I exported a MXF closed-captionned file with 608 and 708 captions. The 608 were fine, but the 708 captions always seems to appears in the "Paint On" mode instead of "Pop On" (in the exported MXF XDCAM 60i file, not in Premiere).
This would be something to fix before the final version.
Thank you
An error occurred while saving the comment Joel Ferland
commented
I updated to 14.8 this morning, and still the same bug. So I still have to rely on Premiere Pro 2018 for my captioning output... Very annoying.
An error occurred while saving the comment Joel Ferland
commented
Nate, have you been able to reproduce the problem? Is this gonna be fixed in the next version?
Thank you
An error occurred while saving the comment Joel Ferland
commented
Here are the files :
https://www.dropbox.com/s/93ur8huyuvvp85g/MCC%20test.zip?dl=0An error occurred while saving the comment Joel Ferland
commented
Here is a MCC file (with 608 and 708 captions) and 2 Premiere projects, in 2018 and 2020. It seems like it's the 708 captions that are offset by a few frames
An error occurred while saving the comment Joel Ferland
commented
These are all 29.97 projects. Caption files are MCC v2, 608/708. In Premiere Pro 2018, the captions files displays and output fine but in 2020 they shift by some frames in the display AND the encoded MXF output. Since I discovered that, I do my final outputs in Premiere Pro 2018. Please correct that.
Thank you.Joel Ferland
shared this idea
·
-
1 voteJoel Ferland
shared this idea
·
-
28 votesJoel Ferland
supported this idea
·
-
3 votesJoel Ferland
supported this idea
·
-
3 votesJoel Ferland
supported this idea
·
-
2 votesJoel Ferland
supported this idea
·
-
20 votes
An error occurred while saving the comment Joel Ferland
commented
I have the same problem here (Premiere 14.9 on macOS).
When the timeline codec matches the export codec, it's fast using "Use previews", but when the export codec isn't the same, then Premieres doesn't use previews (which is more slow than just converting the source codec to the export codec, because it re-renders all effects too).This problem is NOT present with Media Encoder, only in Premiere, so using it is a workaround for more speed.
Here are my results.
In Premiere 14.9 :
22 min. ProRes rendered timeline ==> ProRes file (using previews) : 2 minutes
22 min. ProRes rendered timeline ==> MXF file (using previews) : 40 minutesIn Media Encoder 14.9 :
22 min. ProRes rendered timeline ==> MXF file (using previews) : 15 minutesPlease fix this annoying issue.
Joel Ferland
supported this idea
·
-
2 votesJoel Ferland
supported this idea
·
-
7 votesJoel Ferland
supported this idea
·
-
5 votes
An error occurred while saving the comment Joel Ferland
commented
Updated to 14.8 (macOS) and labels are back!
Joel Ferland
shared this idea
·
-
13 votes
An error occurred while saving the comment Joel Ferland
commented
Updated to 14.8 (macOS) and labels are back!
-
9 votes
An error occurred while saving the comment Joel Ferland
commented
Updated to 14.8 (macOS) and labels are back!
The workaround is indeed working, but since texts and some transparency modes aren't rendered the same with Metal and Software only, it's a dangerous road if everything is not 100% rendered before to switch in software only mode.
Adobe please fix it!