This is Part 2; see Part 1 for an introduction. Methodology My big goal here is to be able to repeatably measure how well various video encoder settings work against the types of videos that I care about. In 2025, I took a single 1080p test video1Included as deception1, below. and ran around a thousand tests against it to see how well various H.265 encoding options worked. This time, I wanted to test against multiple videos and multiple encoders to get a much wider view of encoding performance. Before I started this, I wanted to improve my tooling so I wasn’t wasting time or measuring the wrong thing.
Source: https://scottstuff.net/posts/2026/11/08/video-encoding-2026-part2. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
Read the news here, practice coding, follow structured courses and train for IELTS on our sibling products — all connected through one 8 Sync account.
The ecosystem home: product overviews, blog and full pricing.
ExploreLearn along a clear roadmap: videos, auto-graded quizzes, certificates and mentors who ship for a living.
View the roadmap1,000 DSA problems in Vietnamese, auto-graded across 7 languages — many FREE, right in your browser.
Practice for freeAI grading for all four IELTS skills with detailed rubric feedback.
Try it freeA 22 MB AI IDE for Vietnamese devs.
Download freeOrganizational memory for AI agents.
ExploreAI that staffs your Fanpage and qualifies leads for you.
Try itAudioSilo lets you host your own audiobook library with mobile apps, offline listening, progress syncing, and Docker support.
OccupySaaS is a protest movement in code: laid-off developers building clean-room, open-source, drop-in replacements for the SaaS giants. First up: ZeroAuthy (Auth0) and SalesCompel (Salesforce).
A streaming series is now available for free.
Bối cảnh triển khai AI mà không có bước review rủi ro giống như thiếu một WHERE clause trong SQL có thể dẫn đến đêm dài khắc phục sự cố. Nguyên nhân kỹ thuật nằm ở việc các model AI có thể tạo ra dữ liệu không mong muốn khi không có bộ lọc phù hợp. Hệ quả có thể rất nghiêm trọng khi hệ thống AI vô tình tạo ra nội dung độc hại, sai lệch hoặc vi phạm chính sách. Đáng học hỏi là bài nhấn mạnh việc xác định rõ vị trí của cơ chế "phanh" (brake) trong hệ thống AI và ai chịu trách nhiệm kiểm soát nó.
Bài viết này giải thích tại sao thiếu bước kiểm duyệt trong AI sản xuất có thể dẫn đến hậu quả nghiêm trọng như lỗi query SQL không có WHERE clause.
Announcing TinyGo 0.44 with smaller and faster programs, more multicores on microcontrollers, support for Arduino UNO R4, new drivers, and big Bluetooth updates!
BoxBox is a self-hosted file manager for browsing files already on a Linux server or NAS, without a full cloud suite like Nextcloud. It supports multiple storage locations in one interface, chunked uploads that resume after interruptions, and background jobs with progress updates for moving files. A built-in Monaco-based editor (the same tech used by VS Code) lets you edit configs in the browser. It also supports file and folder sharing with expiring links and ZIP downloads. BoxBox runs as a single Docker container with a Go backend and SvelteKit frontend, needs no separate database, and is released under the MIT license.
Bối cảnh: SailfishOS hỗ trợ phát triển ứng dụng với giao diện GUI viết bằng Qt và daemon xử lý logic bằng Golang. Nguyên nhân kỹ thuật: Kết hợp Qt (cho UI) và Golang (cho daemon) thông qua D-Bus hoặc socket giúp tận dụng ưu điểm ngôn ngữ Go. Hệ quả: Cách tiếp cận này tối ưu hiệu năng khi xử lý tác vụ nặng đồng thời giữ giao diện mượt mà bằng Qt. Điều đáng học: Bài viết hướng dẫn cụ thể cách thiết kế daemon Golang để giao tiếp với Qt thông qua D-Bus hoặc socket, mở ra hướng phát triển ứng dụng đa nền tảng hiệu quả.
Bài hướng dẫn này giúp bạn tích hợp hiệu quả code Golang vào ứng dụng SailfishOS thông qua giao tiếp giữa giao diện Qt và daemon bằng D-Bus hoặc socket.
Roughly 18 months ago, I started working on streaming video from this site. The web side of that is fairly easy — use Shaka Player or similar to handle the JavaScript for playback, and serve up a bunch of .mp4 files with a DASH manifest. You end up with a lot of bytes, but very little actual complexity. They’re all just files that any web server can serve. The hard part turned out to be creating the video files. The problem was (and is) that there are too many choices that need to be made. You need to pick a set of resolutions to serve, you need to pick a set of codecs to support, and then you need to configure each codec at each resolution to get reasonable quality at a reasonable bitrate. None of the choices that need to be made here have a simple, correct answer. Everything ends up involving tradeoffs. This is the first of a set of 7 or 8 posts that aim to explain the tradeoffs, explain the choices that I’ve made for them, offer the data behind the choices, and then try to provide guidance and tools so you can make your own choices. Here’s what I’m planning on posting over the next few weeks: Part 1: Introduction (this post) Part 2: Methodology and Tooling Part 3: H.264 Part 4: H.265 Part 5: AV1 Part 6: Hardware vs Software encoding Part 7: Source Formats and Encoding Quality I may also add another post comparing encoding time on various platforms, depending on how much energy I’m willing to put into it.
Loading comments…