[patch] Few more choices for samplerate, size and fps
Because typing from virtual kbd is hard and i have bad nemory..
Hm, I think I added few more framerates, still can't say why ffmpeg/mpeg2/144 fps do not work... 120/100/90 fps works.. / I also changed default proxy codec to mov (mpeg4/xvid) due to this - while my real 25 fps clip does not hit this limitation if i just change project settings to 144 fps... I returned some logic in ffmpeg.C patch back to initial state, because I still do not understand how this homebrew conversion/check work.. :/ Will post updated patch in its own thread On Monday, June 14, 2021, Andrew Randrianasulu <[email protected]> wrote:
Because typing from virtual kbd is hard and i have bad nemory..
Andrew,
Hm, I think I added few more framerates, still can't say why ffmpeg/mpeg2/144 fps do not work... 120/100/90 fps works.. /
I "think" mpeg2/144 fps worked for me on a sample file. But I am still confused why 16 and 17 fps work (15 is one of the choices) and why 51 fps does not. And also, 1000 works even though it is not in the code now. Oh, well... it is checked into GIT but without the commented out printf. Also checked into GIT, the theme.C additions. I also changed default proxy codec to mov (mpeg4/xvid) due to this - while
my real 25 fps clip does not hit this limitation if i just change project settings to 144 fps...
I did NOT check this BECAUSE the default is documented in the Manual and was highly recommended by IgorBeg when proxy was first established and tested. Is there a problem with leaving proxy.C as it currently is? It seemed to work OK for me just now with the other changes in. If you think it definitely needs to be changed, we will have to discuss with IgorBeg and update the manual. Thanks so much for the quick response ! I am still stuck on multiple issues ... Phyllis
On Tuesday, June 15, 2021, Phyllis Smith via Cin <[email protected]> wrote:
Andrew,
Hm, I think I added few more framerates, still can't say why ffmpeg/mpeg2/144 fps do not work... 120/100/90 fps works.. /
I "think" mpeg2/144 fps worked for me on a sample file. But I am still confused why 16 and 17 fps work (15 is one of the choices) and why 51 fps does not. And also, 1000 works even though it is not in the code now. Oh, well... it is checked into GIT but without the commented out printf.
Also checked into GIT, the theme.C additions.
I also changed default proxy codec to mov (mpeg4/xvid) due to this - while
my real 25 fps clip does not hit this limitation if i just change project settings to 144 fps...
I did NOT check this BECAUSE the default is documented in the Manual and was highly recommended by IgorBeg when proxy was first established and tested. Is there a problem with leaving proxy.C as it currently is? It seemed to work OK for me just now with the other changes in. If you think it definitely needs to be changed, we will have to discuss with IgorBeg and update the manual.
Try to set *clip* fps in asset info window to something unsupported by mpeg2, and try to create proxy - it will trigger same check failure.. :/ Or load resulting rendered odd-fps (like 72 fps) clip to timeline... And proxy that... I found even my copy of pre-compiled ffmpeg 4.4 from termux packages behave.. oddly. if i say Report issues at https://termux.com/issues $ ffmpeg -i vid_20210526.mp4 -c:v mpeg2video -r 144 -f null /dev/null ffmpeg version 4.4 Copyright (c) 2000-2021 the FFmpeg developers built with Android (6454773 based on r365631c2) clang version 9.0.8 ( https://android.googlesource.com/toolchain/llvm-project 98c855489587874b2a325e7a516b99d838599c6f) (based on LLVM 9.0.8svn) configuration: --arch=armeabi-v7a --as=arm-linux-androideabi-clang --cc=arm-linux-androideabi-clang --cxx=arm-linux-androideabi-clang++ --cross-prefix=arm-linux-androideabi- --disable-indevs --disable-outdevs --enable-indev=lavfi --disable-static --disable-symver --enable-cross-compile --enable-gnutls --enable-gpl --enable-libass --enable-libdav1d --enable-libmp3lame --enable-libfreetype --enable-libvorbis --enable-libopus --enable-libx264 --enable-libx265 --enable-libxvid --enable-libvpx --enable-shared --enable-libsoxr --enable-libvidstab --enable-libwebp --prefix=/data/data/com.termux/files/usr --target-os=android --extra-libs=-landroid-glob --enable-neon libavutil 56. 70.100 / 56. 70.100 libavcodec 58.134.100 / 58.134.100 libavformat 58. 76.100 / 58. 76.100 libavdevice 58. 13.100 / 58. 13.100 libavfilter 7.110.100 / 7.110.100 libswscale 5. 9.100 / 5. 9.100 libswresample 3. 9.100 / 3. 9.100 libpostproc 55. 9.100 / 55. 9.100 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'vid_20210526.mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf58.76.100 Duration: 00:00:36.64, start: 0.000000, bitrate: 1314 kb/s Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, unknown/bt470bg/unknown), 640x480 [SAR 27:64 DAR 9:16], 1217 kb/s, 29.58 fps, 29.58 tbr, 11360 tbn, 59.17 tbc (default) Metadata: handler_name : VideoHandle vendor_id : [0][0][0][0] Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 90 kb/s (default) Metadata: handler_name : SoundHandle vendor_id : [0][0][0][0] Stream mapping: Stream #0:0 -> #0:0 (h264 (native) -> mpeg2video (native)) Stream #0:1 -> #0:1 (aac (native) -> pcm_s16le (native)) Press [q] to stop, [?] for help Output #0, null, to '/dev/null': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf58.76.100 Stream #0:0(eng): Video: mpeg2video (Main), yuv420p(tv, unknown/bt470bg/unknown, progressive), 640x480 [SAR 27:64 DAR 9:16], q=2-31, 200 kb/s, 150 fps, 150 tbn (default) Metadata: handler_name : VideoHandle vendor_id : [0][0][0][0] encoder : Lavc58.134.100 mpeg2video Side data: cpb: bitrate max/min/avg: 0/0/200000 buffer size: 0 vbv_delay: N/A Stream #0:1(eng): Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s (default) Metadata: handler_name : SoundHandle vendor_id : [0][0][0][0] encoder : Lavc58.134.100 pcm_s16le frame= 1 fps=0.0 q=0.0 size=N/A time=00:00:00.25 bitrate=N/A speed=1frame= 120 fps=0.0 q=31.0 size=N/A time=00:00:03.96 bitrate=N/A speed=frame= 250 fps=244 q=31.0 size=N/A time=00:00:08.35 bitrate=N/A speed=frame= 353 fps=231 q=31.0 size=N/A time=00:00:12.18 bitrate=N/A speed=frame= 422 fps=208 q=31.0 size=N/A time=00:00:14.50 bitrate=N/A speed=frame= 493 fps=195 q=31.0 size=N/A time=00:00:16.91 bitrate=N/A speed=frame= 566 fps=187 q=31.0 size=N/A time=00:00:19.37 bitrate=N/A speed=frame= 637 fps=180 q=31.0 size=N/A time=00:00:21.78 bitrate=N/A speed=frame= 711 fps=176 q=24.8 size=N/A time=00:00:24.27 bitrate=N/A speed=frame= 784 fps=172 q=31.0 size=N/A time=00:00:26.75 bitrate=N/A speed=frame= 859 fps=170 q=31.0 size=N/A time=00:00:29.29 bitrate=N/A speed=frame= 933 fps=168 q=31.0 size=N/A time=00:00:31.78 bitrate=N/A speed=frame= 1009 fps=166 q=31.0 size=N/A time=00:00:34.34 bitrate=N/A speed=frame= 1084 fps=165 q=31.0 size=N/A time=00:00:36.60 bitrate=N/A speed=frame= 1084 fps=165 q=31.0 Lsize=N/A time=00:00:36.60 bitrate=N/A speed=5.57x video:2437kB audio:4800kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown $ so, 150 fps instead of requested 144! just 'rendering' to default mov/h264 format via removing -f null (format null) and adding output filename like test-fps.mov creates correct (144) fps file o.o if i render to test-fps.mpg it will be reported as 150 fps by ffprobe... Confusing!
Thanks so much for the quick response ! I am still stuck on multiple issues ... Phyllis
Andrew / Andrea, Either this computer is crazy or I am. Using "Proxy" at 1/2 with format set to 72 or 144, the proxy file is created for me using mpeg. Even though there is an error message in the terminal window, it still worked. Does this work for you also? I am still hesitant to change the default from mpeg to mov, but it may be wise to do so. On Mon, Jun 14, 2021 at 11:36 AM Andrew Randrianasulu via Cin < [email protected]> wrote:
Hm, I think I added few more framerates, still can't say why ffmpeg/mpeg2/144 fps do not work... 120/100/90 fps works.. /
I also changed default proxy codec to mov (mpeg4/xvid) due to this - while my real 25 fps clip does not hit this limitation if i just change project settings to 144 fps...
I returned some logic in ffmpeg.C patch back to initial state, because I still do not understand how this homebrew conversion/check work.. :/
Will post updated patch in its own thread
On Monday, June 14, 2021, Andrew Randrianasulu <[email protected]> wrote:
Because typing from virtual kbd is hard and i have bad nemory..
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
On Saturday, June 19, 2021, Phyllis Smith via Cin < [email protected]> wrote:
Andrew / Andrea,
Either this computer is crazy or I am. Using "Proxy" at 1/2 with format set to 72 or 144, the proxy file is created for me using mpeg. Even though there is an error message in the terminal window, it still worked. Does this work for you also?
No, it fails reliably for me at 144 fps media.. (no proxy file appear on disk or in Resources/proxies window). Be sure to delete *proxy*.mpeg from previous run?
I am still hesitant to change the default from mpeg to mov, but it may be wise to do so.
On Mon, Jun 14, 2021 at 11:36 AM Andrew Randrianasulu via Cin < [email protected]> wrote:
Hm, I think I added few more framerates, still can't say why ffmpeg/mpeg2/144 fps do not work... 120/100/90 fps works.. /
I also changed default proxy codec to mov (mpeg4/xvid) due to this - while my real 25 fps clip does not hit this limitation if i just change project settings to 144 fps...
I returned some logic in ffmpeg.C patch back to initial state, because I still do not understand how this homebrew conversion/check work.. :/
Will post updated patch in its own thread
On Monday, June 14, 2021, Andrew Randrianasulu <[email protected]> wrote:
Because typing from virtual kbd is hard and i have bad nemory..
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I would not change mpeg as default. You can always change format manually if you hava problems, but in general mpeg is the most compatible of all.
On Saturday, June 19, 2021, Andrea paz <[email protected]> wrote:
I would not change mpeg as default. You can always change format manually if you hava problems, but in general mpeg is the most compatible of all.
but then adding line about those limitations (mpeg1/2 specifically) in quickstart/manual might be useful? I only see additional colorspace (422) in mpeg as opposed to just yuv420 in mpeg4_xvid in mov as obvious advantage (but may be interlace is also better supported?) ... but ok, this is a bit of niche use (right now)
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith