Were about 90% of the way there. Queries against single and multiple fields can already be done but not quite as diversely as natural language searching. Rewriting of the media database is actually the item i'm currently working on,the goal being to achieve simplicity and diversity (yea I know their usually opposites) without losing any performance. The final design is taking into account that many music collections far exceed 100,000 songs and users expect instant performance. I've done a lot of work with natural language processing as part of speech recognition but it adds overhead so that probably won't be the direction we go.
The official media plugin for windows is based off of directshow which provides support for all of those. The nice part about the modular design is that you can add support for whichever backend you prefer.
The one area I haven't included. Theres 3 options for visualizations, none of which i've considered until just now:
1) Visualizations are added as part of the AV player plugin and respond to the visualize and stop visualize commands
2) Visualizations are their own type of plugin
3) Visualizations fall into the other category (aka implement IOther) as an unofficial part of the framework
All of which would require very very minor changes to add support. My personal preference would be option 1 but that would slightly limit the diversity of standalone visualization engines.



LinkBack URL
About LinkBacks
Reply With Quote
. Theres 3 options for visualizations, none of which i've considered until just now:
Bookmarks