Es geschah am Saturday 10 January 2009 als Luis Garrido schrieb: > Hey, Christian! > > Here I am yet again fooling around with liblinuxsampler, since I am > more keen on using the API directly than passing through LSCP (I have > no need for networking and, besides, I want to create a particular > sort of InstrumentEditor to manipulate the sound on-the-fly further > than can be done with midi controllers, so a remote sampler would be > cumbersome.) > > Would you mind if I ask you a couple of questions? > > Is there a reason why don't you include all headers in > liblinuxsampleraudiodriverinclude_HEADERS at > src/drivers/audio/Makefile.am? I am trying to use > AudioOutputDeviceFactory to get the parameters of the audio driver but > the relevant header won't get installed.
We intentionally didn't want to export details about audio / midi drivers and sampler engine implementations. The idea was to handle all tasks independently of the implementation by just accessing their base class interfaces and their factory classes, the latter hide the creation / destruction of all drivers and engine implementations. Why do you need to access the drivers directly? > As things stand now, I have the impression that only one > InstrumentEditor can be used (per sampler format.) Am I right? Yes, ATM LS will seek the instrument editor factory for all registered instrument editors until it finds one that claims to support the given instrument's format type and data structure. CU Christian ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
