On Wed, 2007-01-03 at 11:52 +0100, Michael Niedermayer wrote: > > (BTW, I think the library will need to provide two > > separate APIs: one for audio and one for video... Or is it possible to > > design a filter API that can support both audio and video?) > > yes 2 seperate APIs make most sense How will this accommodate filters that deal with both audio and video? For example a visualization filter (goom, say) will receive audio as input, and provide the video as output. Cheers, Jason.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4