H.265/HEVC for Premiere Pro compatibility
Hi all, I tried to get an answer on this before I actually subscribed to the mailing list, so I'm told I didn't receive all the replies so I'm just starting over here. I'm using FFmpeg to transcode to H.265 because Premiere's native encoding is incompatible with Vimeo (Vimeo's transcoding causes a color shift in HEVC from Premiere). I also love the constant rate factor encoding option because it'll decide bitrate depending on the resolution needed. I used the command below and VLC and Vimeo both play it (vimeo with no color issues), but if you try to check the encode to the original in Premiere, it imports with sound playing correctly and just a blank green image instead of the video. Any ideas? -i "source.mov" -y -c:v libx265 -preset veryfast -crf 23 -vf format=yuv420p -c:a aac -b:a 320k -ar 48000 -ac 2 -max_muxing_queue_size 1000 "H265.mp4" ᐧ
On 3/28/17, Chris Colton <chris.s.colton@gmail.com> wrote:
Hi all,
I tried to get an answer on this before I actually subscribed to the mailing list, so I'm told I didn't receive all the replies so I'm just starting over here.
I'm using FFmpeg to transcode to H.265 because Premiere's native encoding is incompatible with Vimeo (Vimeo's transcoding causes a color shift in HEVC from Premiere). I also love the constant rate factor encoding option because it'll decide bitrate depending on the resolution needed. I used the command below and VLC and Vimeo both play it (vimeo with no color issues), but if you try to check the encode to the original in Premiere, it imports with sound playing correctly and just a blank green image instead of the video. Any ideas?
Yes, I have an idea? Why you are asking Premiere question in FFmpeg mailing list?
-i "source.mov" -y -c:v libx265 -preset veryfast -crf 23 -vf format=yuv420p -c:a aac -b:a 320k -ar 48000 -ac 2 -max_muxing_queue_size 1000 "H265.mp4" ** _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
I'm asking a Premiere question here because FFmpeg's implementation of HEVC is the only form of HEVC I've ever tried that hasn't automatically worked in Premiere. With FFmpeg you have the ability to fine tune commands to such a great extent that I was hoping someone could help with the problem. ᐧ Thanks, Chris Colton <chris@coltonmp.com> Colton Media Productions <http://www.coltonmediaproductions.com/> +1 970-444-2542 Facebook <http://facebook.com/coltonmediaproductions> | Twitter <http://twitter.com/Chris_Colton> On Tue, Mar 28, 2017 at 11:38 AM, Paul B Mahol <onemda@gmail.com> wrote:
Hi all,
I tried to get an answer on this before I actually subscribed to the mailing list, so I'm told I didn't receive all the replies so I'm just starting over here.
I'm using FFmpeg to transcode to H.265 because Premiere's native encoding is incompatible with Vimeo (Vimeo's transcoding causes a color shift in HEVC from Premiere). I also love the constant rate factor encoding option because it'll decide bitrate depending on the resolution needed. I used
On 3/28/17, Chris Colton <chris.s.colton@gmail.com> wrote: the
command below and VLC and Vimeo both play it (vimeo with no color issues), but if you try to check the encode to the original in Premiere, it imports with sound playing correctly and just a blank green image instead of the video. Any ideas?
Yes, I have an idea? Why you are asking Premiere question in FFmpeg mailing list?
-i "source.mov" -y -c:v libx265 -preset veryfast -crf 23 -vf
format=yuv420p
-c:a aac -b:a 320k -ar 48000 -ac 2 -max_muxing_queue_size 1000 "H265.mp4" ** _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
On Tue, Mar 28, 2017 at 12:00:43 -0600, Chris Colton wrote:
On Tue, Mar 28, 2017 at 11:38 AM, Paul B Mahol <onemda@gmail.com> wrote:
Yes, I have an idea? Why you are asking Premiere question in FFmpeg mailing list?
I'm asking a Premiere question here because FFmpeg's implementation of HEVC is the only form of HEVC I've ever tried that hasn't automatically worked in Premiere. With FFmpeg you have the ability to fine tune commands to such a great extent that I was hoping someone could help with the problem.
No, honestly, it seems to be an issue which only manifests itself with Premiere Pro. Why not ask there? Furthermore, "Pro" implies "Professional", which means it was made either by or for "professionals", i.e. people who earn their living with this. To make things worse, you probably even paid for that software, and it likely even advertises H.265 support. I think you deserve to get an answer from them as to what their requirements are towards an H.265 file. Everything else is just guesswork or reverse engineering. Welcome here anyway, if ffmpeg can help to work around Premiere Pro's shortcomings. ;) (Not saying it couldn't be an ffmpeg issue. Let's see.) Moritz
2017-03-29 0:47 GMT+02:00 Moritz Barsnick <barsnick@gmx.net>:
Everything else is just guesswork or reverse engineering.
But if we'd see the console output of the working command and the non-working, we would know that Premiere only supports some hevc pix_fmts and could help Chris (for free), no? In addition, we could consider adding a warning to the console output. But I complete agree, without console output this is guesswork and should be avoided. Carl Eugen
Thanks Carl, I just didn't know how to catch the console output. Learn something every day. I ran two tests on different files and one converted successfully and Premiere reads it correctly, the other imports as a blank green image. Click on the links below to download the two log files. I used the -report option because I'm not familiar with environment variables, sorry it's so verbose. Log file of conversion that worked correctly: https://www.amazon. com/clouddrive/share/FvX8CqJOavSg0S0WmPiOZPT0Mp0si9vsPdrntZ4nQxG?ref_=cd_ph_ share_link_copy Log file of conversion that can't be read by Premiere, but plays in VLC: https://www.amazon.com/clouddrive/share/6F8nVCyr1m582WUnzJyS27CsOqGaVe vFCil8j3U4hhS?ref_=cd_ph_share_link_copy ᐧ
2017-03-29 22:08 GMT+02:00 Chris Colton <chris.s.colton@gmail.com>:
Thanks Carl, I just didn't know how to catch the console output.
I don't understand: This is trivial both on Windows and osx, what OS are you using? Can you confirm that Premiere does not support yuv422p? Carl Eugen
I'm on Windows 7. Premiere supports 422 in many codecs but I'm not sure if its HEVC support includes 4:2:2. On Wed, Mar 29, 2017 at 4:05 PM, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote:
2017-03-29 22:08 GMT+02:00 Chris Colton <chris.s.colton@gmail.com>:
Thanks Carl, I just didn't know how to catch the console output.
I don't understand: This is trivial both on Windows and osx, what OS are you using?
Can you confirm that Premiere does not support yuv422p?
Carl Eugen _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
ᐧ
On Tue, Mar 28, 2017, at 09:20 AM, Chris Colton wrote:
Hi all,
I tried to get an answer on this before I actually subscribed to the mailing list, so I'm told I didn't receive all the replies so I'm just starting over here.
You never replied to any of our previous questions, including the questions I asked that I know you did receive directly via CC. You only addressed my remark about H.265 as an intermediate and didn't provide the requested info. Because I knew you were not subscribed I mentioned the archives in my message as well. You can view your thread and the replies here: <https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-March/035623.html> Unsubscribed users can click on the email address link at the top to reply to each archived message. The link contains header info to properly keep it within the thread.
Thanks Lou but that link only shows my message, I don't see any replies. I've never used a mailing list like this and I'm new to ffmpeg so I'm sorry I didn't follow procedure. I was just confused. You need the ffmpeg code from converting the file? If so, how do I copy that out of command prompt? This is the only command line utility I've ever used. ᐧ Thanks, Chris Colton <chris@coltonmp.com> Colton Media Productions <http://www.coltonmediaproductions.com/> +1 970-444-2542 Facebook <http://facebook.com/coltonmediaproductions> | Twitter <http://twitter.com/Chris_Colton> On Tue, Mar 28, 2017 at 11:44 AM, Lou <lou@lrcd.com> wrote:
On Tue, Mar 28, 2017, at 09:20 AM, Chris Colton wrote:
Hi all,
I tried to get an answer on this before I actually subscribed to the mailing list, so I'm told I didn't receive all the replies so I'm just starting over here.
You never replied to any of our previous questions, including the questions I asked that I know you did receive directly via CC. You only addressed my remark about H.265 as an intermediate and didn't provide the requested info.
Because I knew you were not subscribed I mentioned the archives in my message as well. You can view your thread and the replies here: <https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-March/035623.html>
Unsubscribed users can click on the email address link at the top to reply to each archived message. The link contains header info to properly keep it within the thread. _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
Thanks Lou but that link only shows my message, I don't see any replies. I've never used a mailing list like this and I'm new to ffmpeg so I'm sorry I didn't follow procedure. I was just confused. You need the ffmpeg code from converting the file? If so, how do I copy that out of command prompt? This is the only command line utility I've ever used. I'm asking a Premiere question here because FFmpeg's implementation of HEVC is the only form of HEVC I've ever tried that hasn't automatically worked in Premiere. With FFmpeg you have the ability to fine tune commands to such a great extent that I was hoping someone could help with the problem. ᐧ On Tue, Mar 28, 2017 at 11:44 AM, Lou <lou@lrcd.com> wrote:
On Tue, Mar 28, 2017, at 09:20 AM, Chris Colton wrote:
Hi all,
I tried to get an answer on this before I actually subscribed to the mailing list, so I'm told I didn't receive all the replies so I'm just starting over here.
You never replied to any of our previous questions, including the questions I asked that I know you did receive directly via CC. You only addressed my remark about H.265 as an intermediate and didn't provide the requested info.
Because I knew you were not subscribed I mentioned the archives in my message as well. You can view your thread and the replies here: <https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-March/035623.html>
Unsubscribed users can click on the email address link at the top to reply to each archived message. The link contains header info to properly keep it within the thread. _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
On Tue, Mar 28, 2017, at 10:06 AM, Chris Colton wrote:
Thanks Lou but that link only shows my message, I don't see any replies.
You need to click on: Next message (by thread): [FFmpeg-user] H.265 Will not Play in Premiere Or view all threads for that month and look for your subject or name: <https://lists.ffmpeg.org/pipermail/ffmpeg-user/2017-March/thread.html#35623> Think of it as somewhat like a forum.
If so, how do I copy that out of command prompt?
I don't know–I don't use Windows (I'm guessing that's what you're using), but I'm sure you can find out how to copy and paste from cmd or redirect the console output to a text file with a search. You're also replying via your coltonmp.com address, but it is not subscribed, so messages from that address may get delayed in the mod queue for a day or less.
On Tue, Mar 28, 2017 at 10:25:44 -0800, Lou wrote:
On Tue, Mar 28, 2017, at 10:06 AM, Chris Colton wrote:
If so, how do I copy that out of command prompt? I don't know–I don't use Windows (I'm guessing that's what you're using), but I'm sure you can find out how to copy and paste from cmd or redirect the console output to a text file with a search.
Actually, it's easier to either a) google for how to text copy out of a console, or even b) use the ffmpeg/ffplay/ffprobe command line option "-report". It will nicely place a log file into the current directory which contains the command line an the complete, uncut console output - even without the line wraps which the Windows cmd console introduces. This text file then should be attached to the response on this list. When all else seems to fail, the "supporters" on this list should recommend using the latter option and attaching the resulting file. Moritz
I'll keep -report in mind that's a great option that I didn't know existed. I just tried converting a different file and Premiere plays it fine. The source that worked was a H.264 (extremely high bitrate) and the one that didn't was DNxHR in .MOV so I'll try it again with DNxHR and see what happens. ᐧ On Tue, Mar 28, 2017 at 1:55 PM, Moritz Barsnick <barsnick@gmx.net> wrote:
On Tue, Mar 28, 2017 at 10:25:44 -0800, Lou wrote:
On Tue, Mar 28, 2017, at 10:06 AM, Chris Colton wrote:
If so, how do I copy that out of command prompt? I don't know–I don't use Windows (I'm guessing that's what you're using), but I'm sure you can find out how to copy and paste from cmd or redirect the console output to a text file with a search.
Actually, it's easier to either a) google for how to text copy out of a console, or even b) use the ffmpeg/ffplay/ffprobe command line option "-report". It will nicely place a log file into the current directory which contains the command line an the complete, uncut console output - even without the line wraps which the Windows cmd console introduces. This text file then should be attached to the response on this list.
When all else seems to fail, the "supporters" on this list should recommend using the latter option and attaching the resulting file.
Moritz _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email ffmpeg-user-request@ffmpeg.org with subject "unsubscribe".
On Tue, 28 Mar 2017 21:55:16 +0200 Moritz Barsnick <barsnick@gmx.net> wrote:
b) use the ffmpeg/ffplay/ffprobe command line option "-report". It will nicely place a log file into the current directory which contains the command line an the complete, uncut console output - even without the line wraps which the Windows cmd console introduces. This text file then should be attached to the response on this list.
When all else seems to fail, the "supporters" on this list should recommend using the latter option and attaching the resulting file.
As convenient as "-report" can be I usually do not recommend it because by default it uses the "verbose" log level which definitely lives up to its name: it's needlessly too verbose for general help. The verbosity usually exceeds my laziness threshold and I tend to just move on to a different question. The FFREPORT environmental variable can be used instead, but I don't know if that works with Windows, and it would probably be too confusing for some users. http://ffmpeg.org/ffmpeg.html#Generic-options
participants (6)
-
Carl Eugen Hoyos -
Chris Colton -
Chris Colton -
Lou -
Moritz Barsnick -
Paul B Mahol