• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Getting ProRes 422 HQ output from LRT (via the dialog and ffmpeg)

Offline
#1 GBlack
The video dialog allows for ProRes but doesn't indicate which profile is being used. I have a use case where ProRes 422 HQ is required. 

Can anyone confirm which profile is being used in the invocation? Is there a way to force 422 HQ encoding?

Thanks

The ffmpeg documentation states the following for the 9.13 ProRes Apple ProRes encoder.

FFmpeg contains 2 ProRes encoders, the prores-aw and prores-ks encoder. The used encoder can be chosen with the -vcodec option.

9.13.1 Private Options for prores-ks

profile integer Select the ProRes profile to encode

‘proxy’
‘lt’
‘standard’
‘hq’
‘4444’
...

Offline
#2 GBlack
To partially answer my own question I see that the log file shows LRT is using the apcn codec which is the Standard Definition flavour. I would like to use the apch codec which is the High Quality (HQ) version.

The log file indicates:
Stream #0:0: Video: prores (apcn / 0x6E637061), yuv422p10le(pc, bt2020c/bt2020/bt2020-10), 4096x2304 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 29.97 fps, 11988 tbn, 29.97 tbc

Anyway to change its choice of codecs or to provide both options?

Thanks
Offline
#3 gwegner
Currently Prores-KS will be used when you choose 444 as color option only, otherwise the default prores Option will be used.
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo
Offline
#4 GBlack
(2017-04-21, 07:48)gwegner Wrote: Currently Prores-KS will be used when you choose 444 as color option only, otherwise the default prores Option will be used.

Excellent!    Hope this wasn't in plain sight in the documentation. I guess it would have been for me if I understood the video codecs better.  

Thank you
Offline
#5 gwegner
I didn't document it because most of the people don't care, I didn't want to confuse anyone... :-)
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo
Offline
#6 GBlack
(2017-04-21, 14:24)gwegner Wrote: I didn't document it because most of the people don't care, I didn't want to confuse anyone... :-)

OK so close, but I'm still having problems with importing into FCP. With the FCP library and project set to Wide Gamut, the imported file shows 709 gamut.

I chose ProRes, 4K, Force 16:9, Ultra High, 444, Wide 2020, no sharpening in the render dialog.

Here is the log:
[2017-04-23 08:38:25] DEBUG: ffmpeg version N-83288-gacf1dd5-tessus Copyright © 2000-2017 the FFmpeg developers
[2017-04-23 08:38:25] DEBUG:   built with Apple LLVM version 8.0.0 (clang-800.0.42.1)
[2017-04-23 08:38:25] DEBUG:   configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libass --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopus --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzmq --enable-version3 --disable-ffplay --disable-indev=qtkit --disable-indev=x11grab_xcb
[2017-04-23 08:38:26] DEBUG:   libavutil      55. 45.100 / 55. 45.100
[2017-04-23 08:38:26] DEBUG:   libavcodec     57. 75.100 / 57. 75.100
[2017-04-23 08:38:26] DEBUG:   libavformat    57. 66.100 / 57. 66.100
[2017-04-23 08:38:26] DEBUG:   libavdevice    57.  2.100 / 57.  2.100
[2017-04-23 08:38:26] DEBUG:   libavfilter     6. 72.100 /  6. 72.100
[2017-04-23 08:38:26] DEBUG:   libswscale      4.  3.101 /  4.  3.101
[2017-04-23 08:38:26] DEBUG:   libswresample   2.  4.100 /  2.  4.100
[2017-04-23 08:38:26] DEBUG:   libpostproc    54.  2.100 / 54.  2.100
[2017-04-23 08:38:31] DEBUG: Input #0, image2, from '/Volumes/Movie HD/LRTimeLapseMovies/LRT_2017-04-22 2020_Test/LRT_%05d.tif':
[2017-04-23 08:38:31] DEBUG:   Duration: 00:00:01.40, start: 0.000000, bitrate: N/A
[2017-04-23 08:38:31] DEBUG:     Stream #0:0: Video: tiff, rgb48le, 7360x4912 [SAR 1:1 DAR 460:307], 25 tbr, 25 tbn, 25 tbc
[2017-04-23 08:38:31] DEBUG: Output #0, mov, to '/var/folders/p5/z8lw_6kr8xl600006s7d56900000gn/T/LRT_Render_4632008677083174802.mov':
[2017-04-23 08:38:31] DEBUG:   Metadata:
[2017-04-23 08:38:31] DEBUG:     creation_time   : "2017-04-23T08:38:25"
[2017-04-23 08:38:31] DEBUG:     encoder         : Lavf57.66.100
[2017-04-23 08:38:31] DEBUG:     Stream #0:0: Video: prores (prores_ks) (ap4h / 0x68347061), yuv444p10le(pc, bt2020c/bt2020/bt2020-10), 4096x2304 [SAR 1:1 DAR 16:9], q=2-31, 200 kb/s, 29.97 fps, 11988 tbn, 29.97 tbc
[2017-04-23 08:38:31] DEBUG:     Metadata:
[2017-04-23 08:38:31] DEBUG:       encoder         : Lavc57.75.100 prores_ks
[2017-04-23 08:38:31] DEBUG: Stream mapping:
[2017-04-23 08:38:31] DEBUG:   Stream #0:0 (tiff) -> scale
[2017-04-23 08:38:31] DEBUG:   crop -> Stream #0:0 (prores_ks)
[2017-04-23 08:38:31] DEBUG: Press [q] to stop, [?] for help
[2017-04-23 08:38:46] DEBUG: [mov @ 0x7fa57c801400] Failed to parse creation_time "2017-04-23T08:38:25"
[2017-04-23 08:40:18] DEBUG: video:218259kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000455%
[2017-04-23 08:40:18] DEBUG: External encoder finished successfully.
[2017-04-23 08:40:21] INFO: Copied temporary file to render directory.
[2017-04-23 08:40:21] INFO: ...deleted temporary file.
[2017-04-23 08:40:21] INFO: Rendered video is located at: /Volumes/Movie HD/LRTimeLapseMovies/2017-04-22 2020_Test_ProRes-444_4K_29.97_UHQ.mov
[2017-04-23 08:40:21] DEBUG: Locating in Finder: /Volumes/Movie HD/LRTimeLapseMovies/2017-04-22 2020_Test_ProRes-444_4K_29.97_UHQ.mov

It definitely says bt2020, but that doesn't appear to be recognized in FCP. I don't really know how to check the file for the containing gamut spec other than importing into FCP. A friend was able to verify the file shows 709 in Adobe Effects. I have the output file on Dropbox if needed.
Offline
#7 gwegner
Ffmpeg seems to write the wrong metadata in some constellations. Don't give too much on what is shown as metadata. If the footage looks okay, go for it.
If fcp doesn't like it out it doesn't look right, try rendering with default gamut from LRTimelapse.

Mobile via Tapatalk.
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo
Offline
#8 GBlack
Hi, To follow up on that suggestion, choosing Std (or Wide) Gamut produces a file that FCP (for me) calls 709.
This time I chose ProRes, 4K, Force 16:9, Ultra High, 444, Std 709, no sharpening in the render dialog.
Offline
#9 GBlack
Anyway, the result is good, even if it's not 2020 Smile
Offline
#10 gwegner
Sounds good.

Mobile via Tapatalk.
Check out my e-book Time Lapse Shooting and Processing!
Subscribe to the LRTimelapse Newsletter!

lrtimelapse.com - advanced Time Lapse Photography made easy!
gwegner.de - Fotografie, Zeitraffer, Video, Reisen.
facebook · Google+ · twitter · vimeo

...also check out: