There are a lot post-processing especial in audio, as Equalization ,Mutichannel down mixer. Typically It should provide a interface to user to select which post-processing and the parameters for the post-processing. If we put them in MIO, It will be hard to dynamically control whether load a post-processing node.
On 3月31日, 下午3时51分, rktb <[email protected]> wrote: > There is technically no limit to the number of nodes that can be > managed. So far, we have not envisioned the player engine directly > marshall more than 3 nodes. However, you may take the case of the > streaming in which we use the streaming manager node. This node in > itself manages 4 other nodes. So, in effect, the player engine has 6 > nodes that it is working with. > > It would depend on the usecase to decide whether the engine directly > needs to control a node, or whether an existing node can share the > burden. For a case of post-processing, maybe the MIO itself can deal > with it. We can discuss more if you provide further details. > > -Ravi > > On Mar 31, 12:42 am, waterblood <[email protected]> wrote: > > > > > Hi All, > > > Currently, all playback pipelines in OpenCORE Engine are three > > nodes mode(ParserNode-->DecNode-->SinkNode). I just wonder if adding > > some post process node to pipeline, whether the engine can works in > > that way? > > > Best Regards > > Guoyin Chen- 隐藏被引用文字 - > > - 显示引用的文字 - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
