Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-27 Thread Luis Garrido
> > Sorry for late response. I just commited those API changes to CVS. > > CU > Christian > Excellent, thanks a lot, will be useful. And it's done when it's done, of course. Luis -- __

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-27 Thread Christian Schoenebeck
Es geschah am Sunday 22 March 2009 als Luis Garrido schrieb: > I think an easy solution would be to modify the following APIs: > > virtual InstrumentEditor* LaunchInstrumentEditor(instrument_id_t ID) > throw (InstrumentManagerException) = 0; > > to > > virtual InstrumentEditor* LaunchInstrumentEdit

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-22 Thread Luis Garrido
Hi again. I met a little inconvenience. The plugin must know whether it has been spawned by a master application or not, so in the latter case it can spawn its own GUI. As things stand now this can be resolved with some negotiation that involves a timeout for the case where the main app is not pr

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-18 Thread Christian Schoenebeck
Es geschah am Wednesday 18 March 2009 als Christian Schoenebeck schrieb: > So, then I propose to change in src/engines/InstrumentManager.h the current > method: > > virtual void LaunchInstrumentEditor(instrument_id_t ID) throw > (InstrumentManagerException) = 0; > > to : > > virtual InstrumentEdito

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-18 Thread Christian Schoenebeck
Es geschah am Wednesday 18 March 2009 als Luis Garrido schrieb: > Perfect, I am not very familiar with pointer wizardry and I read > somewhere that you had to enable rtti in your compiler for this to > work, but that's probably the default setting. Yes, RTTI is enabled by default with g++, no need

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-18 Thread Luis Garrido
> virtual InstrumentEditor* LaunchInstrumentEditor(instrument_id_t ID) throw > (InstrumentManagerException) = 0; > > I could do that change within the next days. Should be done in couple minutes. > That'll be suficient for you? > Sounds about good, thanks a lot. > Of course you can dynamic_cast t

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-18 Thread Christian Schoenebeck
Es geschah am Wednesday 18 March 2009 als Luis Garrido schrieb: > > Well, if we would extend the API by returning back a pointer to the > > launched instrument editor, there would be no need for such an additional > > message passing mechanism. Because you could implement that in your > > applicati

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-18 Thread Luis Garrido
> Well, if we would extend the API by returning back a pointer to the launched > instrument editor, there would be no need for such an additional message > passing mechanism. Because you could implement that in your application > internally, right? Would that be sufficient for you? Great that we a

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-18 Thread Christian Schoenebeck
Es geschah am Tuesday 17 March 2009 als Luis Garrido schrieb: > Correct me if I am wrong. As I see it, the way to spawn an editor from > an app is: > > - Create a plugin dll and install it at the plugin dir in place of > gigedit, since only one single editor is supported. > - In the main applicatio

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-16 Thread Luis Garrido
> But in this case the channel strip and editor are part of the same > application, so you can do your communication between them internally as you > like, without having something to modify about the liblinuxsampler API. Or > what am I missing? > Then it is I who is missing something, which is no

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-16 Thread Christian Schoenebeck
Es geschah am Monday 16 March 2009 als Luis Garrido schrieb: > > The only inconsistency that currently exisists in this case is that the > > virtual keyboard of the instrument editor still sends note on/off events > > to > > Yup, that's what I meant. > > > Why would you want to connect the sampler

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-16 Thread Christian Schoenebeck
Es geschah am Monday 16 March 2009 als Luis Garrido schrieb: > Hi! > > I have been investigating how to convert qgiged into an InstrumentEditor. > > The problem I see with the API right now is that IE is very limited in > its functionality, probably as a consequence of its delicate > interaction wi

Re: [Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-16 Thread Luis Garrido
I guess that my previous message amounts to: Christian, have you any good idea about this problem and have the time and inclination to implement it since I am thoroughly out of my depth here? Otherwise, thinking about it, the idea of an editor plugin which is basically a dbus relay using pInstrum

[Linuxsampler-devel] About LinuxSampler::InstrumentEditor

2009-03-16 Thread Luis Garrido
Hi! I have been investigating how to convert qgiged into an InstrumentEditor. The problem I see with the API right now is that IE is very limited in its functionality, probably as a consequence of its delicate interaction with the sampler process. However these limitations get in the way of a co