On Sat, Dec 17, 2022, 10:35 PM Bob Hepple <bob.hepple@xxxxxxxxx> wrote:
> What if you use libvpx-vp9 for video, opus for audio, and use an mkv file extension? Does it work better?No, it doesn't ...$ wf-recorder -c libvpx-vp9 -C opus -f recording.mkv$ file recording.mkv
recording.mkv: Matroska data... but it still takes a looong time to build the index.On VP9:Maybe I'll just settle on libvpx-vp9 and patch the source so that on SIGINT it prints "SIGINT received: please wait for index building". That's the easiest fix - but maybe we'll get 'oh fedora is soooo sloooow' whinges.On VP8:alabastr gave me the hint that using "--muxer webm" would make v8 work - and it terminates quickly, so this is another possibility.The only question is - is it naf to have a webm in an mp4? Also, is it too naf to patch the source to force '--muxer webm' if codec is detected as libvpx?$ wf-recorder -c libvpx -m webm
Output file "recording.mp4" exists. Overwrite? Y/n: y
selected region 0,0 0x0
Using video filter: null
[libvpx @ 0x7f6d40001e80] v1.12.0
[libvpx @ 0x7f6d40001e80] Neither bitrate nor constrained quality specified, using default CRF of 32 and bitrate of 256kbit/sec
Output #0, webm, to 'recording.mp4':
Stream #0:0: Video: vp8, yuv420p(pc), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 256 kb/s^C$ file recording.mp4
recording.mp4: WebM <<<<< TOO NAF?
It seems reasonable to me. VP8 + Opus on WebM is very well supported. Thou should probably patch the default file extension in the code and documentation too.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
