SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Android Hardware VP9 Accepts Spatial SVC Mode but Drops the Layers

0
·2 views

Android hardware VP9 encoders accept a three-spatial-layer SVC configuration such as L3T3 without error. The bitstream they return is a single flat stream, typically at top resolution with the lower spatial layers missing. Servers expecting multiple layers then treat the stream as broken, even when the network is fine. The behavior has been observed across Samsung, Pixel, Qualcomm, and Tensor devices, and hardware VP9 on Android supports temporal SVC only. Software VP9 (libvpx) produces real spatial layers but costs more CPU and battery, and MediaCodec offers no way to query spatial layering support in advance, so developers must inspect the bitstream to confirm.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Developer builds Chucka, a personal morning briefing that sends a dashboard and voice note via WhatsApp

A developer built a personal automation called Chucka, also known as MorningDashboard, that sends a daily briefing to their own WhatsApp at 7am. The message includes a dashboard image rendered from live Obsidian vault files, covering top tasks, job pipeline and project status, along with a roughly one-minute voice note. The spoken script is generated by an LLM each morning and includes Melbourne weather, then converted to audio with a three-tier text-to-speech chain. The developer later open-sourced the project on 17 October 2026 and found that a message showing as sent only means it was queued, so the runner now waits for delivery confirmation.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Cómo aplicar DDD y arquitectura hexagonal en NestJS con un ejemplo práctico

Un servicio NestJS que empieza con controladores y llamadas directas a Prisma se vuelve difícil de cambiar cuando aparecen reglas de negocio como asignación de técnicos o tareas obligatorias. El artículo propone usar Domain-Driven Design para expresar ese comportamiento y la arquitectura hexagonal para controlar las dependencias. Como ejemplo, desarrolla una API de gestión de servicios con TypeScript, NestJS, Prisma y PostgreSQL, organizada en dos módulos: órdenes de servicio y visitas. Las reglas incluyen prioridades según el nivel de servicio, finalización condicionada a actividades completadas y programación de visitas sin solapamientos. El código completo está disponible en GitHub como implementación educativa.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Python Tutorial Validates Email Lists Using Syntax, DNS and Disposable Checks

A DEV Community how-to explains how to validate an email list in Python without connecting to recipients' mail servers. The method relies on an Apify actor that checks syntax, DNS/MX records, disposable domains and role addresses, avoiding slow SMTP connections that can get a sender's IP flagged. The author notes the tool discloses its own authorship and was built with AI assistance, and that it is a how-to rather than a benchmark. The guide includes sample API code and output, along with statuses such as deliverable_domain, disposable and invalid_domain. It cautions that the tool cannot confirm whether a specific mailbox exists, and that pricing is per validated email.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Applying DDD and Hexagonal Architecture to a NestJS API: A Practical Guide

The guide addresses a common problem in NestJS applications, where services grow to handle business rules, HTTP concerns, and database work together, making changes and testing harder. It uses a service-management API built with TypeScript, NestJS, Prisma, and PostgreSQL as its example, organized into two modules: service-orders and visits. Domain-Driven Design is used to express business behavior as named operations, while Hexagonal Architecture controls dependencies between the business logic and external technologies. The author presents the example as an educational implementation, acknowledging its concrete limitations alongside its benefits. The complete code is published in a GitHub repository called nest-ddd-hexagonal.

0 comments Read more at DEV Community