[FFmpeg-user] Error messages when generating ProRes from 16-Bit TIFF

2020-09-10 Thread Wiesinger, Konstantin - StA
Dear List,

I'm trying to convert from TIFF, 16-Bit, Raw, little endian to ProRes .

Log:

ffmpeg started on 2020-09-10 at 14:21:31
Report written to "ffmpeg-20200910-142131.log"
Log level: 48
Command line:
"C:\\Temp\\ffmpeg\\bin\\ffmpeg.exe" -report -i "D:\\Artus\\tif\\0%05d.tif" -c:v 
prores_ks -profile:v  -vf "scale=2048x1550" -pix_fmt yuv444p10le neu.mov
ffmpeg version git-2020-06-15-9d80f3e Copyright (c) 2000-2020 the FFmpeg 
developers
  built with gcc 9.3.1 (GCC) 20200523
  configuration: --enable-gpl --enable-version3 --enable-sdl2 
--enable-fontconfig --enable-gnutls --enable-iconv --enable-libass 
--enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame 
--enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg 
--enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr 
--enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx 
--enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 
--enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp 
--enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc 
--enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom 
--disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm 
--enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 
--enable-avisynth --enable-libopenmpt --enable-amf
  libavutil  56. 55.100 / 56. 55.100
  libavcodec 58. 92.100 / 58. 92.100
  libavformat58. 46.101 / 58. 46.101
  libavdevice58. 11.100 / 58. 11.100
  libavfilter 7. 86.100 /  7. 86.100
  libswscale  5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc55.  8.100 / 55.  8.100
Splitting the commandline.
Reading option '-report' ... matched as option 'report' (generate a report) 
with argument '1'.
Reading option '-i' ... matched as input url with argument 
'D:\Artus\tif\0%05d.tif'.
Reading option '-c:v' ... matched as option 'c' (codec name) with argument 
'prores_ks'.
Reading option '-profile:v' ... matched as option 'profile' (set profile) with 
argument ''.
Reading option '-vf' ... matched as option 'vf' (set video filters) with 
argument 'scale=2048x1550'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel format) 
with argument 'yuv444p10le'.
Reading option 'neu.mov' ... matched as output url.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option report (generate a report) with argument 1.
Successfully parsed a group of options.
Parsing a group of options: input url D:\Artus\tif\0%05d.tif.
Successfully parsed a group of options.
Opening an input file: D:\Artus\tif\0%05d.tif.
[image2 @ 0219a450e900] Opening 'D:\Artus\tif\01.tif' for reading
[file @ 0219a453a4c0] Setting default whitelist 'file,crypto,data'
[AVIOContext @ 0219a453a5c0] Statistics: 146089658 bytes read, 0 seeks
[tiff @ 0219a45108c0] compression: 1
[image2 @ 0219a450e900] Probe buffer size limit of 500 bytes reached
Input #0, image2, from 'D:\Artus\tif\0%05d.tif':
  Duration: 00:00:01.00, start: 0.00, bitrate: N/A
Stream #0:0, 1, 1/25: Video: tiff, rgb48le, 6440x3780 [SAR 1:1 DAR 46:27], 
25 tbr, 25 tbn, 25 tbc
Successfully opened the file.
Parsing a group of options: output url neu.mov.
Applying option c:v (codec name) with argument prores_ks.
Applying option profile:v (set profile) with argument .
Applying option vf (set video filters) with argument scale=2048x1550.
Applying option pix_fmt (set pixel format) with argument yuv444p10le.
Successfully parsed a group of options.
Opening an output file: neu.mov.
[file @ 0219a4537900] Setting default whitelist 'file,crypto,data'
Successfully opened the file.
detected 48 logical cores
Stream mapping:
  Stream #0:0 -> #0:0 (tiff (native) -> prores (prores_ks))
Press [q] to stop, [?] for help
cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is harmless if it 
occurs once at the start per stream)
cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is harmless if it 
occurs once at the start per stream)
[image2 @ 0219a450e900] Opening 'D:\Artus\tif\02.tif' for reading
[file @ 0219a4538b40] Setting default whitelist 'file,crypto,data'
[tiff @ 0219a4538440] compression: 1
[AVIOContext @ 0219ad3f0c40] Statistics: 146089658 bytes read, 0 seeks
[tiff @ 0219a45a8440] compression: 1
cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is harmless if it 
occurs once at the start per stream)
[image2 @ 0219a450e900] Opening 'D:\Artus\tif\03.tif' for reading
[file @ 0219ad3f0fc0] Setting default whitelist 'file,crypto,data'
[AVIOContext @ 0219ad3f0c40] Statistics: 146089658 bytes read, 0 seeks
[tiff @ 0219ad132440] compression: 1
frame=0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77 bitrate=  
-0.0kbits/s speed=N/A
cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is ha

Re: [FFmpeg-user] Error messages when generating ProRes from 16-Bit TIFF

2020-09-11 Thread Wiesinger, Konstantin - StA
Dear Ted,

> I only have a generic suggestion to offer; as always, try updating to the 
> current code, or a nightly build.
Will do so next occasion and post if output changes
>> Log:
> >
>> ffmpeg started on 2020-09-10 at 14:21:31
>> Report written to "ffmpeg-20200910-142131.log"
> >Log level: 48
>> Command line:
>> "C:\\Temp\\ffmpeg\\bin\\ffmpeg.exe" -report -i "D:\\Artus\\tif\\0%05d.tif" 
>> -c:v prores_ks -profile:v  -vf "scale=2048x1550" -pix_fmt yuv444p10le 
>> neu.mov
>> ffmpeg version git-2020-06-15-9d80f3e Copyright (c) 2000-2020 the FFmpeg 
>> developers
>>  built with gcc 9.3.1 (GCC) 20200523
>>  configuration: --enable-gpl --enable-version3 --enable-sdl2 
>> --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass 
>> --enable-libdav1d --enable-libbluray --enable-libfreetype 
>> --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb 
>> --enable-libopenjpeg --enable-libopus >>--enable-libshine --enable-libsnappy 
>> --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame 
>> --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 
>> --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma 
>> --enable-zlib --enable-gmp --enable-libvidstab --enable->>libvmaf 
>> --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa 
>> --enable-libspeex --enable-libxvid --enable-libaom --disable-w32threads 
>> --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid 
>> --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 
>> --enable-avisynth -->>enable-libopenmpt --enable-amf
>I was curious about a few things though, why might someone add 
>"--disable-w32threads"? Can you use posix threads instead?
As I'm quite new to ffmpeg and cli I'm not sure I get this correctly. I just 
used the zeranoe build so I wasn't even aware of such "details" like 
"--Dis...". Posix thread means output for example via Cygwin on a win machine?

>Also, is 2048x1550 not a typo? (1550 doesn't factor very well, 2×25×31)
>I can't articulate a clear rationale for this (and so it might not be optimal) 
>but I would personally convert formats then change the size, putting the 
>format filter before scale instead of pix_fmt. Or more likely I wouldn't even 
>think of that and expect ffmpeg to figure that part out for me.
I tried to reproduce an external  contractors file: Resizing an original ~6k 
Tiff to a certain section/aperture and this resulted in this odd ratio. Your 
suggestions would be something like: -I xxx -c:v prores_ks -profile:v  
-formatfilter -vf "scale=xxx"?
So you would let ffmpeg decide the default pix_fmt? Do you have any specific 
filters in mind?
>> [AVIOContext @ 0219ad3f0c40] Statistics: 146089658 bytes read, 0 seeks
>> [tiff @ 0219ad19ea80] compression: 1
>> frame=0 fps=0.0 q=0.0 size=   0kB time=-577014:32:22.77 bitrate=  
>> -0.0kbits/s speed=N/A
>> cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is harmless if 
>> it occurs once at the start per stream)
>Again, not sure what it means if anything at all, but the time looks like it 
>rolled over.
Sorry, but what do you mean by "time ... rolled over"?


Kind regards
Konstantin
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".