- https://jakearchibald.com/2020/avif-has-landed/
- jpg, webpとの比較。画像の種類ごとに実例と考察がありわかりやすい。
- Chrome 85以降
- Firefox 77以降
- about:configでフラグを立てる必要あり
#!/bin/sh | |
# 使い方 | |
# cut.sh 開始時間 終了時間 元のファイル | |
# | |
# 例) 1時間32分15秒から、1時間34分5秒まで切り取る | |
# cut.sh 1:32:15 1:34:05 input.mp4 | |
ffmpeg -ss $1 -to $2 -i "$3" -vf fade=d=1.0,reverse,fade=d=1.0,reverse -af afade=d=1.0,areverse,afade=d=1.0,areverse -c:a aac output.mp4 |
ffmpeg -i movie.mp4 -r 1/2 ./frame_%04d.jpg |
One of the headaches I have been bugged by is domain knowledge in SQL queries when it comes to configure code base with Onion Architecture.
If you want to filter data, it is not realistic to use Array.filter
to filter the data after retrieving it by SQL, as it consumes memory and is bad for performance.
I have no choice but to write the filter conditions in the WHERE clause of SQL, but I thought it might be a good idea to define the conditions in the WHERE clause as constants in the domain layer.
Everytime a large language model makes predictions, all of the thousands of tokens in the vocabulary are assigned some degree of probability, from almost 0%, to almost 100%. There are different ways you can decide to choose from those predictions. This process is known as "sampling", and there are various strategies you can use which I will cover here.
Not super comprehensive (yet), but I think having up to date documentation like this should be quite helpful for those out of the loop. Things change all the time in local AI circles, and it can be dizzying to catch up from an outsider's perspective, especially if you are new to the more technical aspects of language models in general (and not just locally hosted LLMs).