AW: [Jsynthlib-devel] General problem with sending SysEx messages?

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

> The only thing which is unclear to me is: why doesn't this=20
> problem appear
> on JSynthLib v0.18?

v0.18 uses different MIDI drivers (not the one of the Java API).

Would be good if you search for such a bug in the=20
bug database of Sun:
http://bugs.sun.com

If you cannot found it there, please report the bug here:
http://bugs.sun.com/services/bugreport/index.jsp

Regards,
Joachim Backhaus

> -----Urspr=FCngliche Nachricht-----
> Von: jsy...@li...
> [mailto:jsy...@li...]Im Auftrag von
> Thorsten Klose
> Gesendet: Montag, 20. Dezember 2004 12:28
> An: jsy...@li...
> Betreff: Re: [Jsynthlib-devel] General problem with sending SysEx
> messages?
>=20
>=20
>=20
> Hi,
>=20
> I've new input on this topic:
>=20
> I noticed the same problem with another Java application which sends
> SysEx messages via the Javasound API. So, this issue is not related
> on JSynthLib itself, but possibly a general problem with Windows/Java
>=20
> Fortunately I also found a solution which works for me: if=20
> the MIDI output
> is sent to MIDI Yoke, the additional data junk won't be=20
> appended (or will=20
> be filtered). So, following MIDI routing helps:
>=20
>     JSynthLib->MIDI Yoke->MIDI-Ox->MIDI Output Port
>=20
> The only thing which is unclear to me is: why doesn't this=20
> problem appear
> on JSynthLib v0.18? Could it be related to the way how v0.18=20
> initializes
> the MIDI Ports?
>=20
> Best Regards, Thorsten.
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from=20
> real users.
> Discover which products truly live up to the hype. Start reading now.=20
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Jsynthlib-devel mailing list
> Jsy...@li...
> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
>=20