AW: [Jsynthlib-devel] Some questions about BankDriver

[Joachim B. <jba...@pi...>]

> Is there a=20
> way to do this?

Yes,

use
Thread.sleep
as you can see in my QuasimidiQuasarSingleDriver.

It helps much to look at other drivers.

Regards,
J. Backhaus

> -----Urspr=FCngliche Nachricht-----
> Von: jsy...@li...
> [mailto:jsy...@li...]Im Auftrag von Joe
> Emenaker
> Gesendet: Mittwoch, 11. Mai 2005 09:52
> An: JSynthLib Development
> Betreff: [Jsynthlib-devel] Some questions about BankDriver
>=20
>=20
> So... I just started trying to make a BankDriver, and I've got some=20
> questions.
>=20
> In this case, there's no way to request an entire bank. Instead, you=20
> have to issue a series of requests for individual patches.=20
> I'm sure that=20
> there are plenty of other devices like this.
>=20
> First question: Is there some way of "throttling" or flow-controlling=20
> the sending of requests. If I send out 100 single-patch requests all=20
> rapid-fire, the hardware device gets confused and doesn't end=20
> up sending=20
> 100 single patches. I need to send a request, wait for the patch to=20
> come, send another request, wait for the patch to come, etc.=20
> Is there a=20
> way to do this?
>=20
> Second question: Since my bank data is composed of multiple single=20
> patches, the bank data matches my sysexID from my=20
> SingleDriver. So, the=20
> banks are being recognized as single patches. Do I have to override=20
> acceptsPatch(Patch p) in my SingleDriver like:
>=20
>     boolean acceptsPatch(Patch p) {
>        return(super.acceptsPatch(p) && p.getMessages().length =3D=3D =
1);
>     }
>=20
> and do similar in the BankDriver? Is there an easier way? The=20
> patchSize=20
> variable would come in handy here, but the patches on this=20
> device vary=20
> in size.
>=20
> - Joe
>=20