[FFmpeg-user] Create a 10-bit VLog test video

[Michael Koch]

Hello all,

I want to create a 10-bit VLog test video which contains 18 levels of 
gray, according to Panasonic's VLog curve.

The curve is documented here:
https://pro-av.panasonic.net/en/cinema_camera_varicam_eva/support/pdf/VARICAM_V-Log_V-Gamut.pdf

I want the leftmost bar to be black (128) and the other 17 bars are for 
-8 to +8 stops, so that the rightmost bar is at level 1023. I'm using 
this command line and the console output is copied below:


ffmpeg -f lavfi -i nullsrc=s=svga,format=gray16 -lavfi 
geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))' 
-pix_fmt yuv444p10le -crf 10 -c:v h264 -t 5 -y VLog_10bit.mov


The video looks perfect when played with FFplay. The leftmost bars are 
indistinguishable on a 8-bit monitor because the levels are too close 
together, but the rightmost bars look as expected.


However when I play the same video with VLC, the two brightest bars at 
the right side have the same shade of gray. I don't understand why. Is 
this a problem in my video, or is it a problem in VLC?


When I extraxt a 16-bit PNG image from the video, this looks as expected 
with 18 levels of gray.

ffmpeg -i VLog_10bit.mov -frames 1 -y out.png

Unrelated: I did try to add the oscilloscope filter at the end of the 
filter chain, but it seems it doesn't work with 16-bit data. There 
should be a warning or an error message. oscilloscope=tw=1:s=1


Michael



C:\Users\astro\Desktop\Test_10-bit>c:\ffmpeg\ffmpeg -f lavfi -i 
nullsrc=s=svga,format=gray16 -lavfi 
geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))' 
-pix_fmt yuv444p10le -crf 10 -c:v h264 -t 10 -y VLog_10bit.mov
ffmpeg version N-99135-gaa8935b395-2020-09-13-gyan-beta2 Copyright (c) 
2000-2020 the FFmpeg developers

  built with gcc 10.2.0 (Rev1, Built by MSYS2 project)
  configuration: --enable-gpl --enable-version3 --enable-sdl2 
--enable-fontconfig --enable-gnutls --enable-iconv --enable-libdav1d 
--enable-libbluray --enable-libfreetype --enable-libmp3lame 
--enable-libass --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 
--enable-libgsm --enable-librav1e --enable-libsvtav1 --enable-avisynth 
--enable-libopenmpt --enable-chromaprint --enable-frei0r 
--enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite 
--enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug 
--enable-librubberband --enable-libssh --enable-libzmq --enable-libzvbi 
--enable-ladspa --enable-libglslang --enable-vulkan --disable-w32threads 
--disable-autodetect --enable-libmfx --enable-ffnvcodec 
--enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc 
--enable-nvdec --enable-dxva2 --enable-amf --enable-static

  libavutil  56. 58.100 / 56. 58.100
  libavcodec 58.106.100 / 58.106.100
  libavformat    58. 54.100 / 58. 54.100
  libavdevice    58. 11.101 / 58. 11.101
  libavfilter 7. 87.100 /  7. 87.100
  libswscale  5.  8.100 /  5.  8.100
  libswresample   3.  8.100 /  3.  8.100
  libpostproc    55.  8.100 / 55.  8.100
Input #0, lavfi, from 'nullsrc=s=svga,format=gray16':
  Duration: N/A, start: 0.00, bitrate: N/A
    Stream #0:0: Video: rawvideo (Y1[0][16] / 0x10003159), gray16le, 
800x600 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc

Stream mapping:
  Stream #0:0 (rawvideo) -> geq
  geq -> Stream #0:0 (libx264)
Press [q] to stop, [?] for help
[libx264 @ 018100489740] using SAR=1/1
[libx264 @ 018100489740] using cpu capabilities: MMX2 SSE2Fast SSSE3 
SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 018100489740] profile High 4:4:4 Predictive, level 3.1, 
4:4:4, 10-bit
[libx264 @ 018100489740] 264 - core 161 r3018 db0d417 - H.264/MPEG-4 
AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - 
options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 
psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 
8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=4 threads=12 
lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 
bluray_compat=0 

Re: [FFmpeg-user] Create a 10-bit VLog test video

[Mick Finn]

Does vlc even support 10 bit playback on supported monitors? I have 10 bit 
calibrated monitor and don’t notice the same difference with vlc as with say 
resolve 

Sent from my iPhone

> On Sep 19, 2020, at 5:10 PM, Michael Koch  wrote:
> 
> Hello all,
> 
> I want to create a 10-bit VLog test video which contains 18 levels of gray, 
> according to Panasonic's VLog curve.
> The curve is documented here:
> https://pro-av.panasonic.net/en/cinema_camera_varicam_eva/support/pdf/VARICAM_V-Log_V-Gamut.pdf
> 
> I want the leftmost bar to be black (128) and the other 17 bars are for -8 to 
> +8 stops, so that the rightmost bar is at level 1023. I'm using this command 
> line and the console output is copied below:
> 
> ffmpeg -f lavfi -i nullsrc=s=svga,format=gray16 -lavfi 
> geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))'
>  -pix_fmt yuv444p10le -crf 10 -c:v h264 -t 5 -y VLog_10bit.mov
> 
> The video looks perfect when played with FFplay. The leftmost bars are 
> indistinguishable on a 8-bit monitor because the levels are too close 
> together, but the rightmost bars look as expected.
> 
> However when I play the same video with VLC, the two brightest bars at the 
> right side have the same shade of gray. I don't understand why. Is this a 
> problem in my video, or is it a problem in VLC?
> 
> When I extraxt a 16-bit PNG image from the video, this looks as expected with 
> 18 levels of gray.
> ffmpeg -i VLog_10bit.mov -frames 1 -y out.png
> 
> Unrelated: I did try to add the oscilloscope filter at the end of the filter 
> chain, but it seems it doesn't work with 16-bit data. There should be a 
> warning or an error message. oscilloscope=tw=1:s=1
> 
> Michael
> 
> 
> 
> C:\Users\astro\Desktop\Test_10-bit>c:\ffmpeg\ffmpeg -f lavfi -i 
> nullsrc=s=svga,format=gray16 -lavfi 
> geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))'
>  -pix_fmt yuv444p10le -crf 10 -c:v h264 -t 10 -y VLog_10bit.mov
> ffmpeg version N-99135-gaa8935b395-2020-09-13-gyan-beta2 Copyright (c) 
> 2000-2020 the FFmpeg developers
>   built with gcc 10.2.0 (Rev1, Built by MSYS2 project)
>   configuration: --enable-gpl --enable-version3 --enable-sdl2 
> --enable-fontconfig --enable-gnutls --enable-iconv --enable-libdav1d 
> --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libass 
> --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 --enable-libgsm --enable-librav1e --enable-libsvtav1 
> --enable-avisynth --enable-libopenmpt --enable-chromaprint --enable-frei0r 
> --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite 
> --enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug 
> --enable-librubberband --enable-libssh --enable-libzmq --enable-libzvbi 
> --enable-ladspa --enable-libglslang --enable-vulkan --disable-w32threads 
> --disable-autodetect --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm 
> --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 
> --enable-amf --enable-static
>   libavutil  56. 58.100 / 56. 58.100
>   libavcodec 58.106.100 / 58.106.100
>   libavformat58. 54.100 / 58. 54.100
>   libavdevice58. 11.101 / 58. 11.101
>   libavfilter 7. 87.100 /  7. 87.100
>   libswscale  5.  8.100 /  5.  8.100
>   libswresample   3.  8.100 /  3.  8.100
>   libpostproc55.  8.100 / 55.  8.100
> Input #0, lavfi, from 'nullsrc=s=svga,format=gray16':
>   Duration: N/A, start: 0.00, bitrate: N/A
> Stream #0:0: Video: rawvideo (Y1[0][16] / 0x10003159), gray16le, 800x600 
> [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc
> Stream mapping:
>   Stream #0:0 (rawvideo) -> geq
>   geq -> Stream #0:0 (libx264)
> Press [q] to stop, [?] for help
> [libx264 @ 018100489740] using SAR=1/1
> [libx264 @ 018100489740] using cpu capabilities: MMX2 SSE2Fast SSSE3 
> SSE4.2 AVX FMA3 BMI2 AVX2
> [libx264 @ 018100489740] profile High 4:4:4 Predictive, level 3.1, 4:4:4, 
> 10-bit
> [libx264 @ 018100489740] 264 - core 161 r3018 

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[Jim DeLaHunt]

On 2020-09-19 01:24, peter.lysyan...@gmail.com wrote:

Dear team,

I was unable to use FFmpeg to convert the * .cin file to * .avi.

Can you please help?


Hello, Peter:

Welcome to the ffmpeg-user list. I am not a great expert on *.cin files 
or on FFmpeg, but I have seen over time that on this list you get better 
help by providing some basic information:


1. Try your task with the current version of FFmpeg as downloaded from 
links on ffmpeg.org.


2. Show us the exact, complete, uncut command line which you used.

3. Show us the exact, complete, uncut output to the terminal from #2.

4. Tell us about the *.cin files. What format is that?  What kind of 
content is in it? Audio? Video? What resolution? What frame rate?


5. What are you expecting will happen?

6. What do you observe actually happening?

I hope that helps you get started. Good luck!
  —Jim DeLaHunt


___
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".

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[Reto Kromer]

peter.lysyan...@gmail.com wrote:

>I was unable to use FFmpeg to convert the * .cin file to
>* .avi.

Cineon (.cin) was a predecessor of DPX, introduced by Kodak as
a digital postproduction format for cinema movies in the early
1990s, and today it's essentially one of its flavours.

Best regards, Reto

___
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".

[FFmpeg-user] how to convert *.cin into *.avi?

[peter.lysyansky]

Dear team,

I was unable to use FFmpeg to convert the * .cin file to * .avi.

 

Can you please help?

 

Thank you,

 

Peter Lysyansky, PhD

Algorithmic solutions

+972 54 729 9573

 

___
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".

[FFmpeg-user] ffprobe timeout is not working

[gilmotta]

Hello Everybody,

I'm afraid this is a recurring subject but -timeout and -stimeout is not
working for me. I look at older posts but no luck.

I tried seconds, milliseconds and micro seconds but no matter what I do
ffprobe returns immediately when I type the command with -timeout or
-stimeout

/var/www/ffmpeg-4.3/ffprobe -timeout 3000 -v error -i
rtmp://localhost/streams/stream1
[rtmp @ 0x587f5c0] Cannot open connection
tcp://localhost:1935?listen_timeout=-64771072
rtmp://localhost/fds/stream1: Address already in use

When I type without -timeout if the stream is streaming it returns
graciously but if the stream is not streaming it hangs forever so I need to
timeout or my stream checker script will not work.

Could anyone shed some light, please? 

Thanks a lot,



--
Sent from: http://www.ffmpeg-archive.org/
___
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".

Re: [FFmpeg-user] Create a 10-bit VLog test video

[Paul B Mahol]

On Sat, Sep 19, 2020 at 12:10 PM Michael Koch 
wrote:

> Hello all,
>
> I want to create a 10-bit VLog test video which contains 18 levels of
> gray, according to Panasonic's VLog curve.
> The curve is documented here:
>
> https://pro-av.panasonic.net/en/cinema_camera_varicam_eva/support/pdf/VARICAM_V-Log_V-Gamut.pdf
>
> I want the leftmost bar to be black (128) and the other 17 bars are for
> -8 to +8 stops, so that the rightmost bar is at level 1023. I'm using
> this command line and the console output is copied below:
>
> ffmpeg -f lavfi -i nullsrc=s=svga,format=gray16 -lavfi
> geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))'
>
> -pix_fmt yuv444p10le -crf 10 -c:v h264 -t 5 -y VLog_10bit.mov
>
> The video looks perfect when played with FFplay. The leftmost bars are
> indistinguishable on a 8-bit monitor because the levels are too close
> together, but the rightmost bars look as expected.
>
> However when I play the same video with VLC, the two brightest bars at
> the right side have the same shade of gray. I don't understand why. Is
> this a problem in my video, or is it a problem in VLC?
>
> When I extraxt a 16-bit PNG image from the video, this looks as expected
> with 18 levels of gray.
> ffmpeg -i VLog_10bit.mov -frames 1 -y out.png
>
> Unrelated: I did try to add the oscilloscope filter at the end of the
> filter chain, but it seems it doesn't work with 16-bit data. There
> should be a warning or an error message. oscilloscope=tw=1:s=1
>

That happened only with gray>8 formats and have been fixed already.


>
> Michael
>
>
>
> C:\Users\astro\Desktop\Test_10-bit>c:\ffmpeg\ffmpeg -f lavfi -i
> nullsrc=s=svga,format=gray16 -lavfi
> geq=lum='st(0,trunc(18*X/W));64*(128*eq(ld(0),0)+132*eq(ld(0),1)+136*eq(ld(0),2)+144*eq(ld(0),3)+160*eq(ld(0),4)+192*eq(ld(0),5)+240*eq(ld(0),6)+298*eq(ld(0),7)+363*eq(ld(0),8)+433*eq(ld(0),9)+505*eq(ld(0),10)+578*eq(ld(0),11)+652*eq(ld(0),12)+726*eq(ld(0),13)+800*eq(ld(0),14)+874*eq(ld(0),15)+949*eq(ld(0),16)+1023*eq(ld(0),17))'
>
> -pix_fmt yuv444p10le -crf 10 -c:v h264 -t 10 -y VLog_10bit.mov
> ffmpeg version N-99135-gaa8935b395-2020-09-13-gyan-beta2 Copyright (c)
> 2000-2020 the FFmpeg developers
>built with gcc 10.2.0 (Rev1, Built by MSYS2 project)
>configuration: --enable-gpl --enable-version3 --enable-sdl2
> --enable-fontconfig --enable-gnutls --enable-iconv --enable-libdav1d
> --enable-libbluray --enable-libfreetype --enable-libmp3lame
> --enable-libass --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
> --enable-libgsm --enable-librav1e --enable-libsvtav1 --enable-avisynth
> --enable-libopenmpt --enable-chromaprint --enable-frei0r
> --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite
> --enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug
> --enable-librubberband --enable-libssh --enable-libzmq --enable-libzvbi
> --enable-ladspa --enable-libglslang --enable-vulkan --disable-w32threads
> --disable-autodetect --enable-libmfx --enable-ffnvcodec
> --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc
> --enable-nvdec --enable-dxva2 --enable-amf --enable-static
>libavutil  56. 58.100 / 56. 58.100
>libavcodec 58.106.100 / 58.106.100
>libavformat58. 54.100 / 58. 54.100
>libavdevice58. 11.101 / 58. 11.101
>libavfilter 7. 87.100 /  7. 87.100
>libswscale  5.  8.100 /  5.  8.100
>libswresample   3.  8.100 /  3.  8.100
>libpostproc55.  8.100 / 55.  8.100
> Input #0, lavfi, from 'nullsrc=s=svga,format=gray16':
>Duration: N/A, start: 0.00, bitrate: N/A
>  Stream #0:0: Video: rawvideo (Y1[0][16] / 0x10003159), gray16le,
> 800x600 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc
> Stream mapping:
>Stream #0:0 (rawvideo) -> geq
>geq -> Stream #0:0 (libx264)
> Press [q] to stop, [?] for help
> [libx264 @ 018100489740] using SAR=1/1
> [libx264 @ 018100489740] using cpu capabilities: MMX2 SSE2Fast SSSE3
> SSE4.2 AVX FMA3 BMI2 AVX2
> [libx264 @ 018100489740] profile High 4:4:4 Predictive, level 3.1,
> 4:4:4, 10-bit
> [libx264 @ 018100489740] 264 - core 161 r3018 db0d417 - H.264/MPEG-4
> AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html -
> options: cabac=1 ref=3 deblock=1:0:0 

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[Jim DeLaHunt]

On 2020-09-19 02:26, peter.lysyan...@gmail.com wrote:


...
The FFmpeg command:

>ffmpeg -i usimage21010021041935.cin usimage21010021041935.avi

And the result is:

"usimage21010021041935.cin: Invalid data found when processing input"


[…image deleted…]

For the next time, please do not send a screen shot of a Command Prompt 
window. Instead, copy the text from the Command Prompt window and paste 
that text into your message. It is easier to read and modify text than a 
picture (of a Command Prompt window). Giving readers of the list text 
instead of a picture reduces the work they have to do in order to 
understand your situation. It demonstrates respect, and might lead to 
more offers of help.


Fortunately, the FFmpeg run you posted was short and simple, so people 
who want to help will probably look at the screen shot.


It looks like the FFmpeg version you are running is dated 2020-08-31. 
(I'd copy and paste the exact version string, but I can't, because it's 
a picture not text.) That is recent, but not current. One step you can 
take is to get the absolute latest copy of FFmpeg and try again. It's 
possible that a relevant bug in FFmpeg got fixed in the last three weeks.


The error message, "Invalid data found when processing input", implies 
to me that 1. FFmpeg thinks it supports this file format, and 2. that 
the file you supplied appears to not conform to that file format.


How confident are you that the contents of the file are correctly formatted?

Does this same command line succeed with other *.cin files which you have?

One final suggestion. It's great that you have sample files for testing 
by the people who help you. However, it is better to put them on a 
server somewhere and send a link to the file, instead of attaching the 
file to a message sent to the list. 9MB of attachments * many hundreds 
or thousands of subscribers to this list = a lot of disk space around 
the world consumed by these attachments. What I typically do is put the 
file in a public folder on my free Dropbox account, and have Dropbox 
give me a sharing link to that file.  Then I can send just the link.


I hope this is helpful for you. Best regards,
    —Jim DeLaHunt


___
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".

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[Paul B Mahol]

Hi,

On Sat, Sep 19, 2020 at 11:12:05AM +0200, Reto Kromer wrote:
> peter.lysyan...@gmail.com wrote:
> 
> >I was unable to use FFmpeg to convert the * .cin file to
> >* .avi.
> 
> Cineon (.cin) was a predecessor of DPX, introduced by Kodak as
> a digital postproduction format for cinema movies in the early
> 1990s, and today it's essentially one of its flavours.

Do you have by any chance Cineon muxed into .mov container?

Some examples:

C310:GL3N

cini:bsmt

D210:GL3N
___
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".

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[peter.lysyansky]

If you ask me- this is my first experience with FFmpeg, so I have no idea about 
your question.

Actually I will appreciate some practical instructions.

I desperately need the acquired data in any reasonable format.

Thank you,
Peter

-Original Message-
From: ffmpeg-user  On Behalf Of Paul B Mahol
Sent: Saturday, September 19, 2020 10:46 PM
To: FFmpeg user questions 
Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi?

Hi,

On Sat, Sep 19, 2020 at 11:12:05AM +0200, Reto Kromer wrote:
> peter.lysyan...@gmail.com wrote:
> 
> >I was unable to use FFmpeg to convert the * .cin file to
> >* .avi.
> 
> Cineon (.cin) was a predecessor of DPX, introduced by Kodak as a 
> digital postproduction format for cinema movies in the early 1990s, 
> and today it's essentially one of its flavours.

Do you have by any chance Cineon muxed into .mov container?

Some examples:

C310:GL3N

cini:bsmt

D210:GL3N
___
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".

___
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".

[FFmpeg-user] Segment at Scene Change

[Michael Davis via ffmpeg-user]

HI all,

I am either not asking the question in a way Google can understand, or no one 
has asked this, as every issue I can find is in regards to outputting images of 
each scene.  I want to output video segments…

I have an input video that is basically a slide show, except the slides 
coincide with songs, so they are not at regular intervals.  I would like to 
segment and create a sequence of ts files that are split based on a scene 
change threshold, and have a separate ts file for each song.


Thanks,
Mike
___
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".

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[Paul B Mahol]

On Sat, Sep 19, 2020 at 11:56:24PM +0300, peter.lysyan...@gmail.com wrote:
> Thank you for helpful recommendations.
> 
> This is my first experience with FFmpeg
> 
> Please see my comments below.
> 
>  
> 
> Best regards,
> 
> Peter
> 
>  
> 
> From: Jim DeLaHunt  
> Sent: Saturday, September 19, 2020 10:25 PM
> To: peter.lysyan...@gmail.com
> Cc: ffmpeg-user@ffmpeg.org
> Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi?
> 
>  
> 
> On 2020-09-19 02:26, peter.lysyan...@gmail.com 
>   wrote:
> 
> ...
> The FFmpeg command: 
> 
> >ffmpeg -i usimage21010021041935.cin usimage21010021041935.avi
> 
> And the result is:
> 
> "usimage21010021041935.cin: Invalid data found when processing input"
> 
> […image deleted…]
> 
> For the next time, please do not send a screen shot of a Command Prompt 
> window. Instead, copy the text from the Command Prompt window and paste that 
> text into your message. It is easier to read and modify text than a picture 
> (of a Command Prompt window).  Giving readers of the list text instead of a 
> picture reduces the work they have to do in order to understand your 
> situation. It demonstrates respect, and might lead to more offers of help.
> 
> Fortunately, the FFmpeg run you posted was short and simple, so people who 
> want to help will probably look at the screen shot.
> 
> It looks like the FFmpeg version you are running is dated 2020-08-31. (I'd 
> copy and paste the exact version string, but I can't, because it's a picture 
> not text.) That is recent, but not current. One step you can take is to get 
> the absolute latest copy of FFmpeg and try again. It's possible that a 
> relevant bug in FFmpeg got fixed in the last three weeks.
> 
> Here is my version: ffmpeg version git-2020-08-31-4a11a6f Copyright (c) 
> 2000-2020 the FFmpeg developers
> 
> built with gcc 10.2.1 (GCC) 20200805
> 
> How can I get the latest version?
> 
> The error message, "Invalid data found when processing input", implies to me 
> that 1. FFmpeg thinks it supports this file format, and 2. that the file you 
> supplied appears to not conform to that file format.  
> 
> How confident are you that the contents of the file are correctly formatted?
> 
> All cin files are exported from the official SonoTouch ultrasound scanner, 
> but I cannot confirm they are correct. Can ffmpeg display details - what's 
> wrong in the file?
> 
> Does this same command line succeed with other *.cin files which you have?
> 
> Yes, I checked other files- the result is the same.
> 
> One final suggestion. It's great that you have sample files for testing by 
> the people who help you. However, it is better to put them on a server 
> somewhere and send a link to the file, instead of attaching the file to a 
> message sent to the list. 9MB of attachments * many hundreds or thousands of 
> subscribers to this list = a lot of disk space around the world consumed by 
> these attachments. What I typically do is put the file in a public folder on 
> my free Dropbox account, and have Dropbox give me a sharing link to that 
> file.  Then I can send just the link.
> 
> Below is the link to demo.cin file in my Dropbox:
> 
> https://www.dropbox.com/s/dta1swkn2ohl91l/demo.cin?dl=0

This file is not Cineon for sure.
Also its entropy never rises above 0.5

> 
> I hope this is helpful for you. Best regards,
> —Jim DeLaHunt
> 
>  
> 
> ___
> 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".
___
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".

Re: [FFmpeg-user] bwdif filter question

[Mark Filipak (ffmpeg)]

On 09/18/2020 03:01 PM, Carl Eugen Hoyos wrote:

Am 16.09.2020 um 15:58 schrieb Mark Himsley :

On Mon, 14 Sep 2020 at 15:42, Mark Filipak (ffmpeg)  wrote:
Is the input to the bwdif filter fields or frames?

The input to every filter in a filter chain is a raster of pixels.
That raster may contain one frame or two fields.

That may not be wrong (apart from Paul’s comment) but I wonder how useful it is:
No matter if the raster contains one field, two interlaced fields or a 
progressive frame, the filter will always see an input frame.


"...if the raster contains *one field*...the filter will always see an input 
*frame*."
How is that possible? How can a frame contain just one field?


The fact that there is metadata that may signal the content is also not 
necessarily helpful as this metadata is typically wrong (often signalling 
fields when a frame is provided).


Can you provide an example (or a link to an example)? I've examined a great number of DSM mpeg 
presentation streams ('VOB's & 'm2ts's) and I've not seen a single case. What metadata are you 
looking at?

sequence_extension: 'progressive_sequence'?
picture_coding_extension: 'picture_structure'?
picture_coding_extension: 'top_field_first'?
picture_coding_extension: 'repeat_first_field'?
picture_coding_extension: 'progressive_frame'?


That’s why the filter ignores the information by default.

(If you provide only one field, no FFmpeg deinterlacer will produce useful 
output.)


The bwdif filter will interpret a single raster and is designed to
output two rasters, each containing one or the other of the fields
that were contained in the input raster.


"...interpret a *single raster*...one or the other of the fields...in the *input 
raster*."
Mark Himsley, how are you defining "raster"? I thought you were equating a "single raster" with a 
frame and "two rasters" with fields, but now I'm unsure what you mean.



You can request that the filter outputs one instead of two rasters for one 
input raster.


--
COVID-19 perspective, 0 AM UTC, 20 September 2020.
Yesterday, China: 14 new cases, S.Korea: 110, U.S.: 42,533.
Today, U.S.: 4% of world population, 22% of cases, 21% of deaths.
Today, U.S.: Of 4,427,517 resolved cases, 95% lived, 5% died.
22 Jan: U.S. & S.Korea reported 1st cases on the same day.
6 Mar, S.Korea: 140,000 total tests; results in 4 hours.
6 Mar, U.S.: 2000 total tests; results in 1 to 2 weeks.
May, for the first time, U.S. care-homes are required to report.
1 Jun, total care-home deaths, S.Korea: 0, U.S.: 26,000 to 40,000.
5 Aug, U.S. tests still only 1/4 of number needed; 4 day results.
1 Sep, over 60% of U.S. nurses still lack protective equipment.
18 Sep, U.S. doctors & nurses still acutely lack PPE; 1200 dead.
___
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".

Re: [FFmpeg-user] Transcoding mpeg2video in mpegts to h264 in mpegts has fast playback

[Patrick Double]

> On Sep 18, 2020, at 1:37 PM, Carl Eugen Hoyos  wrote:
> 
> 
> 
>> Am 18.09.2020 um 18:51 schrieb Pat Double :
>> 
>> Here is my sample:
>> 
>> https://www.dropbox.com/s/7s7itvj1uy2nov7/RobotMaker-short.ts
> 
> Please provide an input sample, never provide output files unless 
> specifically requested.

This is an input sample. If you’ll look at the video stream you’ll see it’s 
mpeg2video which is what I’ve stated is the input. The output I desire is h264.

> And please remove -hide_banner from your command line when asking questions 
> here.

My first command output includes the banner. I didn’t think it was necessary to 
include multiple copies of the banner but in the future I will remove 
-hide_banner from all commands.


___
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".

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[Paul B Mahol]

On Sat, Sep 19, 2020 at 11:14:03PM +0300, peter.lysyan...@gmail.com wrote:
> If you ask me- this is my first experience with FFmpeg, so I have no idea 
> about your question.
> 
> Actually I will appreciate some practical instructions.
> 
> I desperately need the acquired data in any reasonable format.

There is a problem.

IIRC you have not provided any cineon sample files.

Also do know that Cineon can store completely custom color space
into bitstream. And to get proper representation for your display
device there are some conversion that needs to be done somehow.

FFmpeg currently does not have any support for Cineon (.cin file extension
with magic bytes 0x802a5fd7 at start) at all.

You could try GraphicsMagick or ImageMagick.

> 
> Thank you,
> Peter
> 
> -Original Message-
> From: ffmpeg-user  On Behalf Of Paul B Mahol
> Sent: Saturday, September 19, 2020 10:46 PM
> To: FFmpeg user questions 
> Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi?
> 
> Hi,
> 
> On Sat, Sep 19, 2020 at 11:12:05AM +0200, Reto Kromer wrote:
> > peter.lysyan...@gmail.com wrote:
> > 
> > >I was unable to use FFmpeg to convert the * .cin file to
> > >* .avi.
> > 
> > Cineon (.cin) was a predecessor of DPX, introduced by Kodak as a 
> > digital postproduction format for cinema movies in the early 1990s, 
> > and today it's essentially one of its flavours.
> 
> Do you have by any chance Cineon muxed into .mov container?
> 
> Some examples:
> 
> C310:GL3N
> 
> cini:bsmt
> 
> D210:GL3N
> ___
> 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".
> 
> ___
> 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".
___
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".

Re: [FFmpeg-user] how to convert *.cin into *.avi?

[peter.lysyansky]

Thank you for helpful recommendations.

This is my first experience with FFmpeg

Please see my comments below.

 

Best regards,

Peter

 

From: Jim DeLaHunt  
Sent: Saturday, September 19, 2020 10:25 PM
To: peter.lysyan...@gmail.com
Cc: ffmpeg-user@ffmpeg.org
Subject: Re: [FFmpeg-user] how to convert *.cin into *.avi?

 

On 2020-09-19 02:26, peter.lysyan...@gmail.com 
  wrote:

...
The FFmpeg command: 

>ffmpeg -i usimage21010021041935.cin usimage21010021041935.avi

And the result is:

"usimage21010021041935.cin: Invalid data found when processing input"

[…image deleted…]

For the next time, please do not send a screen shot of a Command Prompt window. 
Instead, copy the text from the Command Prompt window and paste that text into 
your message. It is easier to read and modify text than a picture (of a Command 
Prompt window).  Giving readers of the list text instead of a picture reduces 
the work they have to do in order to understand your situation. It demonstrates 
respect, and might lead to more offers of help.

Fortunately, the FFmpeg run you posted was short and simple, so people who want 
to help will probably look at the screen shot.

It looks like the FFmpeg version you are running is dated 2020-08-31. (I'd copy 
and paste the exact version string, but I can't, because it's a picture not 
text.) That is recent, but not current. One step you can take is to get the 
absolute latest copy of FFmpeg and try again. It's possible that a relevant bug 
in FFmpeg got fixed in the last three weeks.

Here is my version: ffmpeg version git-2020-08-31-4a11a6f Copyright (c) 
2000-2020 the FFmpeg developers

built with gcc 10.2.1 (GCC) 20200805

How can I get the latest version?

The error message, "Invalid data found when processing input", implies to me 
that 1. FFmpeg thinks it supports this file format, and 2. that the file you 
supplied appears to not conform to that file format.  

How confident are you that the contents of the file are correctly formatted?

All cin files are exported from the official SonoTouch ultrasound scanner, but 
I cannot confirm they are correct. Can ffmpeg display details - what's wrong in 
the file?

Does this same command line succeed with other *.cin files which you have?

Yes, I checked other files- the result is the same.

One final suggestion. It's great that you have sample files for testing by the 
people who help you. However, it is better to put them on a server somewhere 
and send a link to the file, instead of attaching the file to a message sent to 
the list. 9MB of attachments * many hundreds or thousands of subscribers to 
this list = a lot of disk space around the world consumed by these attachments. 
What I typically do is put the file in a public folder on my free Dropbox 
account, and have Dropbox give me a sharing link to that file.  Then I can send 
just the link.

Below is the link to demo.cin file in my Dropbox:

https://www.dropbox.com/s/dta1swkn2ohl91l/demo.cin?dl=0

I hope this is helpful for you. Best regards,
—Jim DeLaHunt

 

___
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".