
Recherche avancée
Autres articles (67)
-
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (6506)
-
Evolution #4753 (Nouveau) : Styles du privé : listes d’objets (suite des boîtes et des formulaires)
30 avril 2021Les boîtes et les formulaires ont été visuellement « raccordés » ensembles.
Je pense que logiquement les listes d’objets devraient suivre.
En fait ce sont 3 variations d’un même composant : une boîte avec entête, corps et pied.Pour les listes on peut séparer la question en 2 aspects :
1) L’emballage extérieur¶
Là il s’agirait de reprendre les choix graphiques propres à « l’emballage extérieur » des boîtes et formulaires : bordure, arrondi, espacements.
Exemple sur l’image suivant où les 3 sont visibles (nb : ceux en colonne sont automatiquement « ressérés », d’où la différence de padding etc.)Après en fonction de l’un ou de l’autre, il y aura peut-être lieu d’ajuster le padding ou la taille du titre. Mais pour l’instant ce sont ceux en place.
2) L’intérieur¶
Ensuite je propose de procéder à quelques ajustements à l’intérieur de ces listes.
Je pense que certains choix ont été faits pour s’accommoder du manque de place en largeur à l’époque, et ne sont plus nécessaires maintenant.Pour me faire un idée de ce qui fonctionnerait le mieux, et comprendre les détails visuels qui me gênaient un peu, j’ai parcouru quelques articles de recommandations sur l’ergonomie des data tables.
Alors ils traitent plutot des fonctionnalités de ces tables dans leur ensemble, mais il y a aussi quelques guidelines visuelles intéressantes.- https://uxdesign.cc/data-table-for-enterprise-ux-cb48fb9fdf1e
- https://medium.com/nextux/design-better-data-tables-4ecc99d23356
- https://www.uxbooth.com/articles/designing-user-friendly-data-tables/
- https://uxdesign.cc/lets-design-data-tables-bf065a60e588
Je retiens quelques règles simples :
- Des espacements suffisants et consistants (le padding quoi)
- Une taille de police identique partout (au moins dans le tbody). C’est fatiguant pour l’oeil et moins lisible quand on passe sans arrêt d’un taille de police à l’autre sur une même ligne. Et je ne suis pas sûr qu’il y ait forcément besoin de gras pour certains éléments comme les titres ou autres.
- À quelques exceptions près (id, picto), pas de largeur fixes sur les colonnes, laisser faire le navigateur.
Donc voilà, c’est pas grand chose à ajuster non plus.
Les colonnes des tables ont des classes .importante et .secondaire.
À mon avis elle ne devraient plus avoir d’incidence en vue « normale », mais juste décider quelles colonnes afficher et masquer en vue réduite, dans les colonnes ou ailleurs.Donc dans les grandes lignes ça donnerait quelques chose comme ça (juste une maquette) :
3) Détails¶
Enfin pour ces 3 composants, je propose qu’il y ait une classe modificatrice commune pour produire un affichage compact, c’est à dire ressérer tout le contenu.
Cette classe serait automatiquement appliquée dans les colonnes.Ça pourrait être « compact », mais sur d’autres composants pour varier les tailles je suis parti sur mini / large. Donc mini aussi ?
-
My SBC Collection
31 décembre 2023, par Multimedia Mike — GeneralLike many computer nerds in the last decade, I have accumulated more than a few single-board computers, or “SBCs”, which are small computers based around a system-on-a-chip (SoC) that nearly always features an ARM CPU at its core. Surprisingly few of these units are Raspberry Pi units, though that brand has come to exemplify and dominate the product category.
Also, as is the case for many computer nerds, most of these SBCs lay fallow for years at a time. Equipped with an inexpensive lightbox that I procured in the last year, I decided I could at least create glamour shots of various units and catalog them in a blog post.
While Raspberry Pi still enjoys the most mindshare far and away, and while I do have a few Raspberry Pi units in my inventory, I have always been a bigger fan of the ODROID brand, which works with convenient importers around the world (in the USA, I can vouch for Ameridroid, to whom I’ve forked over a fair amount of cash for these computing toys).
As mentioned, Raspberry Pi undisputedly has the most mindshare of all these SBC brands and I often wonder why… and then I immediately remind myself that it has the biggest ecosystem, and has a variety of turnkey projects and applications (such as Pi-hole and PiVPN) that promise a lower barrier to entry — as well as a slightly lower price point — than some of these other options. ODROID had a decent ecosystem for awhile, especially considering the monthly ODROID Magazine, though that ceased publication in July 2020. The Raspberry Pi and its variants were famously difficult to come by due to the global chip shortage from 2021-2023. Meanwhile, I had no trouble procuring these boards during the same timeframe.
So let’s delve into the collection…
Cubieboard
The Raspberry Pi came out in 2012 and by 2013 I was somewhat coveting one to hack on. Finally ! An accessible ARM platform to play with. I had heard of the BeagleBoard for years but never tried to get my hands on one. I was thinking about taking the plunge on a new Raspberry Pi, but a colleague told me I should skip that and go with this new hotness called the Cubieboard, based on an Allwinner SoC. The big value-add that this board had vs. a Raspberry Pi was that it had a SATA adapter. Although now that it has been a decade, it only now occurs to me to quander whether it was true SATA or a USB-to-SATA bridge. Looking it up now, I’m led to believe that the SoC supported the functionality natively.Anyway, I did get it up and running but never did much with it, thus setting the tone for future SBC endeavors. No photos because I gave it to another tech enthusiast years ago, whose SBC collection dwarfs my own.
ODROID-XU4
I can’t recall exactly when or how I first encountered the ODROID brand. I probably read about it on some enthusiast page or another circa 2014 and decided to try one out. I eventually acquired a total of 3 of these ODROID-XU4 units, each with a different case, 1 with a fan and 2 passively-cooled :This is based on the Samsung Exynos 5422 SoC, the same series as was used in their Note 3 phone released in 2013. It has been a fun chip to play with. The XU4 was also my first introduction to the eMMC storage solution that is commonly supported on the ODROID SBCs (alongside micro-SD). eMMC offers many benefits over SD in terms of read/write speed as well as well as longevity/write cycles. That’s getting less relevant these days, however, as more and more SBCs are being released with direct NVMe SSD support.
I had initially wanted to make a retro-gaming device built on this platform (see the handheld section later for more meditations on that). In support of this common hobbyist goal, there is this nifty case XU4 case which apes the aesthetic of the Nintendo N64 :
It even has a cool programmable LCD screen. Maybe one day I’ll find a use for it.
For awhile, one of these XU4 units (likely the noisy, fan-cooled one) was contributing results to the FFmpeg FATE system.
While it features gigabit ethernet and a USB3 port, I once tried to see if I could get 2 Gbps throughput with the unit using a USB3-gigabit dongle. I had curious results in that the total amount of traffic throughput could never exceed 1 Gbps across both interfaces. I.e., if 1 interface was dealing with 1 Gbps and the other interface tried to run at 1 Gbps, they would both only run at 500 Mbps. That remains a mystery to me since I don’t see that limitation with Intel chips.
Still, the XU4 has been useful for a variety of projects and prototyping over the years.
ODROID-HC2 NAS
I find that a lot of my fellow nerds massively overengineer their homelab NAS setups. I’ll explore this in a future post. For my part, people tend to find my homelab NAS solution slightly underengineered. This is the ODROID-HC2 (the “HC” stands for “Home Cloud”) :It has the same guts as the ODROID-XU4 except no video output and the USB3 function is leveraged for a SATA bridge. This allows you to plug a SATA hard drive directly into the unit :
Believe it or not, this has been my home NAS solution for something like 6 or 7 years now– I don’t clearly remember when I purchased it and put it into service.
But isn’t this sort of irresponsible ? What about a failure of the main drive ? That’s why I have an external drive connected for backing up the most important data via rsync :
The power consumption can’t be beat– Profiling for a few weeks of average usage worked out to 4.5 kWh for the ODROID-HC2… per month.
ODROID-C2
I was on a kick of ordering more SBCs at one point. This is the ODROID-C2, equipped with a 64-bit Amlogic SoC :I had this on the FATE farm for awhile, performing 64-bit ARM builds (vs. the XU4’s 32-bit builds). As memory serves, it was unreliable and would occasionally freeze up.
Here is a view of the eMMC storage through the bottom of the translucent case :
ODROID-N2+
Out of all my ODROID SBCs, this is the unit that I long to “get back to” the most– the ODROID-N2+ :Very capable unit that makes a great little desktop. I have some projects I want to develop using it so that it will force me to have a focused development environment.
Raspberry Pi
Eventually, I did break down and get a Raspberry Pi. I had a specific purpose in mind and, much to my surprise, I have stuck to it :I was using one of the ODROID-XU4 units as a VPN gateway. Eventually, I wanted to convert the XU4 to something else and I decided to run the VPN gateway as an appliance on the simplest device I could. So I procured this complete hand-me-down unit from eBay and went to work. This was also the first time I discovered the DietPi distribution and this box has been in service running Wireguard via PiVPN for many years.
I also have a Raspberry Pi 3B+ kicking around somewhere. I used it as a Steam Link device for awhile.
SOPINE + Baseboard
Also procured when I was on this “let’s buy random SBCs” kick. The Pine64 SOPINE is actually a compute module that comes in the form factor of a memory module.Back to using Allwinner SoCs. In order to make this thing useful, you need to place it in something. It’s possible to get a mini-ITX form factor board that can accommodate 7 of these modules. Before going to that extreme, there is this much simpler baseboard which can also use eMMC for storage.
I really need to find an appropriate case for this one as it currently performs its duty while sitting on an anti-static bag.
NanoPi NEO3
I enjoy running the DietPi distribution on many of these SBCs (as it’s developed not just for Raspberry Pi). I have also found their website to be a useful resource for discovering new SBCs. That’s how I found the NanoPi series and zeroed in on this NEO3 unit, sporting a Rockchip SoC, and photographed here with some American currency in order to illustrate its relative size :I often forget about this computer because it’s off in another room, just quietly performing its assigned duty.
MangoPi MQ-Pro
So far, I’ve heard of these fruits prepending the Greek letter pi for naming small computing products :- Raspberry – the O.G.
- Banana – seems to be popular for hobbyist router/switches
- Orange
- Atomic
- Nano
- Mango
Okay, so the AtomicPi and NanoPi names don’t really make sense considering the fruit convention.
Anyway, the newest entry is the MangoPi. These showed up on Ameridroid a few months ago. There are 2 variants : the MQ-Pro and the MQ-Quad. I picked one and rolled with it.
When it arrived, I unpacked it, assembled the pieces, downloaded a distro, tossed that on a micro-SD card, connected a monitor and keyboard to it via its USB-C port, got the distro up and running, configured the wireless networking with a static IP address and installed sshd, and it was ready to go as a headless server for an edge application.
The unit came with no instructions that I can recall. After I got it set up, I remember thinking, “What is wrong with me ? Why is it that I just know how to do all of this without any documentation ?”
Only after I got it up and running and poked around a bit did I realize that this SBC doesn’t have an ARM SoC– it’s a RISC-V SoC. It uses the Allwinner D1, so it looks like I came full circle back to Allwinner.
So I now have my first piece of RISC-V hobbyist kit, although I learned recently from Kostya that it’s not that great for multimedia.
Handheld Gaming Units
The folks at Hardkernel have also produced a series of handheld retro-gaming devices called ODROID-GO. The first one resembled the original Nintendo Game Boy, came as a kit to be assembled, and emulated 5 classic consoles. It also had some hackability to it. Quite a cool little device, and inexpensive too. I have since passed it along to another gaming enthusiast.Later came the ODROID-GO Advance, also a kit, but emulating more devices. I was extremely eager to get my hands on this since it could emulate SNES in addition to NES. It also features a headphone jack, unlike the earlier model. True to form, after I received mine, it took me about 13 months before I got around to assembling it. After that, the biggest challenge I had was trying to find an appropriate case for it.
Even though it may try to copy the general aesthetic and form factor of the Game Boy Advance, cases for the GBA don’t fit this correctly.
Further, Hardkernel have also released the ODROID-GO Super and Ultra models that do more and more. The Advance, Super, and Ultra models have powerful SoCs and feature much more hackability than the first ODROID-GO model.
I know that the guts of the Advance have been used in other products as well. The same is likely true for the Super and Ultra.
Ultimately, the ODROID-GO Advance was just another project I assembled and then set aside since I like the idea of playing old games much more than actually doing it. Plus, the fact has finally crystalized in my mind over the past few years that I have never enjoyed handheld gaming and likely will never enjoy handheld gaming, even after I started wearing glasses. Not that I’m averse to old Game Boy / Color / Advance games, but if I’m going to play them, I’d rather emulate them on a large display.
The Future
In some of my weaker moments, I consider ordering up certain Banana Pi products (like the Banana Pi BPI-R2) with a case and doing my own router tricks using some open source router/firewall solution. And then I remind myself that my existing prosumer-type home router is doing just fine. But maybe one day…The post My SBC Collection first appeared on Breaking Eggs And Making Omelettes.
-
Why does ffmpeg keep using more and more RAM and crash ?
29 décembre 2022, par József Márton KakasI am using the following command with ffmpeg to encode a video file using the libsvtav1 codec :
ffmpeg -i hevc.mkv -map 0:v:0 -c:v:0 libsvtav1 -preset 8 -crf 22 -format matroska av1.mkv
.

However, ffmpeg is using up all of my available RAM and crashing. I have also tried using the libx264 codec, but the same issue occurs, although it happens more slowly. I have already allocated 12 GB of RAM to ffmpeg, but it still seems to be insufficient. How can I prevent ffmpeg from using all of my available RAM and crashing when using either the libsvtav1 or libx264 codecs ?


I have tried it on another VM, but the same issue occurs. Here is the full output of the program.


ffmpeg -i akira.mkv -map 0:v:0 -c:v:0 libsvtav1 -preset 8 -crf 22 -c:a copy -c:s copy -format matroska av1.mkv
ffmpeg version n5.1.2-7-ga6e26053c2-20221106 Copyright (c) 2000-2022 the FFmpeg developers
 built with gcc 12.2.0 (crosstool-NG 1.25.0.90_cf9beb1)
 configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --disable-chromaprint --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-mbedtls --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --disable-openal --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags=-pie --extra-libs='-ldl -lgomp' --extra-version=20221106
 libavutil 57. 28.100 / 57. 28.100
 libavcodec 59. 37.100 / 59. 37.100
 libavformat 59. 27.100 / 59. 27.100
 libavdevice 59. 7.100 / 59. 7.100
 libavfilter 8. 44.100 / 8. 44.100
 libswscale 6. 7.100 / 6. 7.100
 libswresample 4. 7.100 / 4. 7.100
 libpostproc 56. 6.100 / 56. 6.100
Input #0, matroska,webm, from 'akira.mkv':
 Metadata:
 title : Akira 4K
 encoder : libebml v1.3.10 + libmatroska v1.5.2
 creation_time : 2020-05-04T19:57:18.000000Z
 Duration: 02:04:46.50, start: 0.000000, bitrate: 10945 kb/s
 Stream #0:0: Video: hevc (Main 10), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2074 [SAR 1:1 DAR 1920:1037], 23.98 fps, 23.98 tbr, 1k tbn (default)
 Metadata:
 BPS-eng : 9531297
 DURATION-eng : 02:04:46.479000000
 NUMBER_OF_FRAMES-eng: 179496
 NUMBER_OF_BYTES-eng: 8919482644
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:1(eng): Subtitle: subrip
 Metadata:
 BPS-eng : 46
 DURATION-eng : 01:59:00.755000000
 NUMBER_OF_FRAMES-eng: 1277
 NUMBER_OF_BYTES-eng: 41675
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:2(ita): Audio: ac3, 48000 Hz, 5.1(side), fltp, 448 kb/s (default)
 Metadata:
 title : Nuovo doppiaggio
 BPS-eng : 448000
 DURATION-eng : 02:04:28.480000000
 NUMBER_OF_FRAMES-eng: 233390
 NUMBER_OF_BYTES-eng: 418234880
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:3(ita): Audio: ac3, 48000 Hz, stereo, fltp, 448 kb/s
 Metadata:
 title : Doppiaggio Storico
 BPS-eng : 448000
 DURATION-eng : 02:04:28.480000000
 NUMBER_OF_FRAMES-eng: 233390
 NUMBER_OF_BYTES-eng: 418234880
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:4(ita): Subtitle: dvd_subtitle, 1920x1080
 Metadata:
 title : Italiano
 BPS-eng : 8426
 DURATION-eng : 02:00:14.955000000
 NUMBER_OF_FRAMES-eng: 1201
 NUMBER_OF_BYTES-eng: 7599491
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:5(ita): Subtitle: subrip (default)
 Metadata:
 title : Forced
 BPS-eng : 0
 DURATION-eng : 01:46:31.753000000
 NUMBER_OF_FRAMES-eng: 14
 NUMBER_OF_BYTES-eng: 462
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:6(jpn): Audio: eac3, 48000 Hz, 5.1(side), fltp, 256 kb/s
 Metadata:
 BPS-eng : 256000
 DURATION-eng : 02:04:46.496000000
 NUMBER_OF_FRAMES-eng: 233953
 NUMBER_OF_BYTES-eng: 239567872
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:7(eng): Audio: eac3, 48000 Hz, 5.1(side), fltp, 256 kb/s
 Metadata:
 BPS-eng : 256000
 DURATION-eng : 02:04:46.496000000
 NUMBER_OF_FRAMES-eng: 233953
 NUMBER_OF_BYTES-eng: 239567872
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 Stream #0:8: Video: mjpeg (Baseline), yuvj444p(pc, bt470bg/unknown/unknown), 1067x600, 90k tbr, 90k tbn (attached pic)
 Metadata:
 filename : cover_land.jpg
 mimetype : image/jpeg
 Stream #0:9: Video: mjpeg (Baseline), yuvj444p(pc, bt470bg/unknown/unknown), 120x176, 90k tbr, 90k tbn (attached pic)
 Metadata:
 filename : small_cover.jpg
 mimetype : image/jpeg
 Stream #0:10: Video: mjpeg (Baseline), yuvj444p(pc, bt470bg/unknown/unknown), 213x120, 90k tbr, 90k tbn (attached pic)
 Metadata:
 filename : small_cover_land.jpg
 mimetype : image/jpeg
 Stream #0:11: Video: mjpeg (Baseline), yuvj444p(pc, bt470bg/unknown/unknown), 600x882, 90k tbr, 90k tbn (attached pic)
 Metadata:
 filename : cover.jpg
 mimetype : image/jpeg
 Stream #0:12: Attachment: otf
 Metadata:
 filename : StoneSansStd-Semibold.otf
 mimetype : application/vnd.ms-opentype
 Stream #0:13: Attachment: otf
 Metadata:
 filename : StoneSansStd-SemiboldItalic.otf
 mimetype : application/vnd.ms-opentype
 Stream #0:14: Attachment: otf
 Metadata:
 filename : ATPacella-Black.otf
 mimetype : application/vnd.ms-opentype
 Stream #0:15: Attachment: ttf
 Metadata:
 filename : ITC Franklin Gothic LT Medium Condensed.ttf
 mimetype : application/x-truetype-font
File 'av1.mkv' already exists. Overwrite? [y/N] y
Stream mapping:
 Stream #0:0 -> #0:0 (hevc (native) -> av1 (libsvtav1))
Press [q] to stop, [?] for help
Svt[info]: -------------------------------------------
Svt[info]: SVT [version]: SVT-AV1 Encoder Lib v1.3.0
Svt[info]: SVT [build] : GCC 12.2.0 64 bit
Svt[info]: LIB Build date: Nov 6 2022 00:41:54
Svt[info]: -------------------------------------------
Svt[info]: Number of logical cores available: 16
Svt[info]: Number of PPCS 71
Svt[info]: [asm level on system : up to avx]
Svt[info]: [asm level selected : up to avx]
Svt[info]: -------------------------------------------
Svt[info]: SVT [config]: main profile tier (auto) level (auto)
Svt[info]: SVT [config]: width / height / fps numerator / fps denominator : 3840 / 2080 / 24000 / 1001
Svt[info]: SVT [config]: bit-depth / color format : 10 / YUV420
Svt[info]: SVT [config]: preset / tune / pred struct : 8 / PSNR / random access
Svt[info]: SVT [config]: gop size / mini-gop size / key-frame type : 161 / 16 / key frame
Svt[info]: SVT [config]: BRC mode / rate factor : CRF / 22 
Svt[info]: -------------------------------------------
Output #0, matroska, to 'av1.mkv':
 Metadata:
 title : Akira 4K
 encoder : Lavf59.27.100
 Stream #0:0: Video: av1 (AV01 / 0x31305641), yuv420p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x2074 [SAR 1:1 DAR 1920:1037], q=2-31, 23.98 fps, 1k tbn (default)
 Metadata:
 BPS-eng : 9531297
 DURATION-eng : 02:04:46.479000000
 NUMBER_OF_FRAMES-eng: 179496
 NUMBER_OF_BYTES-eng: 8919482644
 _STATISTICS_WRITING_APP-eng: mkvmerge v43.0.0 ('The Quartermaster') 32-bit
 _STATISTICS_WRITING_DATE_UTC-eng: 2020-05-04 19:57:18
 _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES
 encoder : Lavc59.37.100 libsvtav1
frame= 1 fps=0.0 q=0.0 size= 1kB time=00:00:00.00 bitrate=N/A sframe= 2 fps=1.3 q=0.0 size= 1kB time=00:00:00.00 bitrate=N/A sframe= 51 fps= 25 q=0.0 size= 1kB time=00:00:00.00 bitrate=N/A sframe= 73 fps= 16 q=16.0 size= 1kB time=00:00:00.00 bitrate=7480frame= 76 fps= 14 q=16.0 size= 1kB time=00:00:00.00 bitrate=7480frame= 81 fps= 14 q=16.0 size= 1kB time=00:00:00.00 bitrate=7480frame= 87 fps= 14 q=21.0 size= 1kB time=00:00:00.16 bitrate= 44frame= 95 fps= 14 q=21.0 size= 1kB time=00:00:00.50 bitrate= 14frame= 100 fps= 13 q=16.0 size= 1kB time=00:00:00.66 bitrate= 11frame= 110 fps= 13 q=23.0 size= 1kB time=00:00:00.96 bitrate= 7frame= 114 fps= 13 q=23.0 size= 1kB time=00:00:01.12 bitrate= 6frame= 122 fps= 13 q=23.0 size= 1kB time=00:00:01.46 bitrate= 5frame= 126 fps= 12 q=23.0 size= 1kB time=00:00:01.62 bitrate= 4frame= 133 fps= 12 q=22.0 size= 1kB time=00:00:01.92 bitrate= 3frame= 139 fps= 12 q=21.0 size= 1kB time=00:00:02.17 bitrate= 3frame= 141 fps= 11 q=22.0 size= 1kB time=00:00:02.25 bitrate= 3frame= 144 fps= 11 q=23.0 size= 1kB time=00:00:02.37 bitrate= 3frame= 151 fps= 11 q=13.0 size= 1kB time=00:00:02.67 bitrate= 2frame= 159 fps= 11 q=18.0 size= 1kB time=00:00:03.00 bitrate= 2frame= 164 fps= 11 q=22.0 size= 1kB time=00:00:03.21 bitrate= 2frame= 174 fps= 11 q=22.0 size= 1kB time=00:00:03.63 bitrate= 2frame= 179 fps= 11 q=20.0 size= 1kB time=00:00:03.83 bitrate= 1frame= 187 fps= 11 q=20.0 size= 1kB time=00:00:04.17 bitrate= 1frame= 189 fps= 10 q=21.0 size= 1kB time=00:00:04.25 bitrate= 1frame= 192 fps= 10 q=22.0 size= 1kB time=00:00:04.38 bitrate= 1frame= 195 fps=8.0 q=20.0 size= 1kB time=00:00:04.50 bitrate= 1frame= 201 fps=8.0 q=11.0 size= 1kB time=00:00:04.67 bitrate= 1Killeds/s speed=0.187x