AOMedia Releases AV2 Encoder 1.0, But Experts Say It Is Not Pipeline-Ready Yet

·1 views

AOMedia published the AV2 reference encoder version 1.0.0 on May 28, 2026, marking a significant milestone in open video codec development. Early evaluations show AV2 delivers roughly 28–33% better compression efficiency than AV1 at equivalent quality, with gains exceeding 40% on screen content. However, the release is a reference implementation, meaning it is intentionally slow, lacks FFmpeg integration, and has no shipping hardware decoders available. Developers are advised to hold off on pipeline changes and instead optimize existing AV1 and H.264 workflows in the near term. The situation closely mirrors the early days of AV1's rollout, where real-world adoption lagged well behind the initial specification release.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Fix CORS Errors in React Apps: Backend Headers, Proxies and More

CORS errors are a common frustration for React developers, occurring when browsers block frontend requests to APIs that work fine in tools like Postman or curl. The root cause is a browser security policy that requires servers to explicitly allow cross-origin requests via response headers such as Access-Control-Allow-Origin. The correct fix lies on the backend, where developers using Node.js, Flask, or Laravel can add CORS middleware or headers to permit requests from their frontend origin. During local development, a proxy entry in package.json can route requests through React's dev server as a workaround, though this does not apply to production builds. Public CORS proxy services exist as a last resort but are discouraged for production use due to latency, rate limits, and security concerns.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Topicary Brings Structured Authoring to Technical Writers Without XML

Topicary is a content authoring tool that applies structured authoring principles — long associated with XML-based systems like DITA — without requiring users to write any markup. The platform lets writers save reusable content blocks called components, which automatically update across all referencing topics when the source is edited. It also supports conditional content filtering by audience, product, or platform, with changes reflected instantly in the editor without a separate build step. Variables allow single-point updates for recurring values like product names or version numbers across an entire project. Topicary can import existing content from formats including Markdown, DITA, MadCap Flare, Confluence, Word, and OpenAPI 3.x specifications.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Microsoft Launches Production-Ready AI Agent Harness and Hosted Agents at Build 2026

Microsoft announced the General Availability of Agent Harness and Foundry Hosted Agents at its Build 2026 conference, marking a shift from experimental tooling to a fully supported production runtime. Agent Harness is a single binary handling the operational core of AI agents, including function invocation, context compaction, history persistence, tool approval, and built-in OpenTelemetry observability. Foundry Hosted Agents offers the same capabilities as a managed, consumption-based cloud service accessible via a single API call. Both products run locally, in containers, or as a hosted service, and support multi-agent orchestration with connectors for GitHub Copilot and the Claude Agent SDK. The release addresses longstanding production challenges teams faced when deploying AI agents, positioning the infrastructure layer — not the AI model itself — as the core product.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Spring AI Tips to Cut LLM Costs by Managing Output Tokens and Chat Memory

A developer guide published on DEV Community outlines practical strategies for controlling large language model (LLM) costs using Spring AI, focusing on output tokens, reasoning tokens, and conversation history. Output tokens typically cost five to eight times more than input tokens, and reasoning models compound this by generating hidden thinking tokens billed at the same higher rate. Spring AI offers a provider-independent maxTokens cap and provider-specific reasoning controls, such as OpenAI's reasoning-effort setting and Anthropic's thinking-token budget, to limit runaway response costs. The guide warns that a Spring AI 2.0 upgrade raised Anthropic's default maxTokens from 500 to 4096, potentially multiplying response costs for users who relied on the old cap without realising it. Developers are also cautioned to disable reasoning during local Ollama development, since models like qwen3 and deepseek-r1 use reasoning by default, making hidden token usage easy to overlook before moving to a billed production environment.

0 comments Read more at DEV Community