You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2019. It is now read-only.
Even when the codec works in master mode and can generate a 44.1kHz frame and associated bit clock, the format for the topology file prevents us from creating pipelines, DAIs and PCM devices working with 44.1 frames per ms.
Example of problematic macros, it's not clear how 48 might be replaced by 44.1...
this is related to issue 60, which I'm in the middle of finishing. So the idea is to remove the frame count altogether from pipeline definition. I have a branch for this in my personal github account, but I don't won't to do PR yet as it needs much more testing. I have to do now now couple of more urgent things, but will continue with this in 1 or weeks.
Even when the codec works in master mode and can generate a 44.1kHz frame and associated bit clock, the format for the topology file prevents us from creating pipelines, DAIs and PCM devices working with 44.1 frames per ms.
Example of problematic macros, it's not clear how 48 might be replaced by 44.1...
This may have an impact of SOF as well since we assume the number of frames per ms is integer.
The text was updated successfully, but these errors were encountered: