From: Takashi Iwai Subject: Re: alsa-lib support for compress offload Date: Fri, 16 Jan 2015 11:34:21 +0100 Message-ID: References: <54B8DF7A.6000700@imgtec.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 3FE80265019 for ; Fri, 16 Jan 2015 11:34:22 +0100 (CET) In-Reply-To: <54B8DF7A.6000700@imgtec.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Qais Yousef Cc: alsa-devel@alsa-project.org, Mark Brown List-Id: alsa-devel@alsa-project.org At Fri, 16 Jan 2015 09:52:58 +0000, Qais Yousef wrote: > > Hi, > > As far as I understand I need to use something similar to tinycompress > to use alsa devices that supports compress offload. When I asked on > gstreamer list [1] about alsasink support for compress offload they said > yes. But I can see that gstalsasink.c [2] only uses the standard > alsa-lib api which AFAICT doesn't support compress offload. > > Did I misread the code and alsa-lib actually works with compress > offload? Gstreamer refers to the feature "passthrough" and associate it > with SPDIF[3], are they taking advantage of some other alsa feature that > looks like compress offload? It's a normal IEC958 passthrough, nothing to do with the compress offload. And, no, we have no support for compress API in alsa-lib yet. Just because no one submitted the patches. Takashi