Re: How to handle complex Codec2Codec

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 29, 2024 at 04:51:49AM +0000, Kuninori Morimoto wrote:

> This is OK, but how to handle below ?
> 
> 	+----------------------+
> 	|CPU                   |     +------+
> 	|  +--[rate convert]<--| <-- |Codec1| <--
> 	|  |                   |     +------+
> 	|  |                   |     +------+
> 	|  +------------------>| --> |Codec2| -->
> 	+----------------------+     +------+

> I think there are 2 issues.
> 	(1) How to handle [CPU] part     on Codec2Codec ?
> 	(2) How to handle [rate convert] on Codec2Codec ?

At the minute this would be a DPCM thing.  I've never actively worked on
a system with DPCM so I'm not as up to speed as I could be but with my
current understanding I'd expect the rate conversion to be done as a
backend fixup on the DAI link for the first CODEC and just a straight
pass through for the second.

> I think (2) [rate convert] needs DPCM connection,
> but how to use it with Codec2Codec ?

The whole thing is a bit fragile so I don't know how well those two play
together.  Though your picture doesn't look like it's actually doing a
codec2codec link?  It probably should ideally (with the SRC being a
CODEC in the graph) but not right now.

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Pulse Audio]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux