• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
RE: Re: Midisport and sysex
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Re: Midisport and sysex


  • Subject: RE: Re: Midisport and sysex
  • From: "Peter Karlsson" <email@hidden>
  • Date: Wed, 22 Dec 2004 09:22:27 +0100

The problem here is that I don't know what synthesizer or other module is
connected to my app. Because this is a multi device library editor. So I
can't just send out a sysex message for some device and hope for an answer
that will fix the MIDISport problem. A workaround is a rather complicated
thing in my case.

So I suggest that you keep on working for a MIDISport fix. After all, it's
a MIDISport problem. And I feel sorry for all costumers all around the
world that keeps buying MIDISports without knowing that it's not working
properly, like myself. At least they have the right to know about the
problems before they buy but that is not the case here.

The nice thing is that a app don't have to know what MIDI interface is
connected. But if we must make workarounds for a particular interface the
whole idea is gone. I can be wrong but I think we must solve the problem
where it begins.

Peter

Ursprungligt meddelande

> circa 12/21/04 6:13 AM, "Peter Karlsson" <email@hidden> wrote:
>
> > Now I have this MIDISport 4x4 and this will not work either. And I
can't get
> > my workaround to fix the sysex problem. Open question to M-Audio. What
is
> > M-AUDIO going to do about it?
>
> I missed this message for a while because was posted to mutliple lists and
> it got pulled into my Cocoa folder where it was almost lost in the
shuffle.
> My apologies.
>
> We of course cannot promise a fix for this problem in any particular
> time-frame. I am not even sure what the problem is yet. When you say your
> attempted work-around has failed, what are the details? I had suggested
that
> you attempt to perform some harmless transaction with your synth once and
> then try a second time if you receive no response after a second. Does
your
> synth support such a transaction? If so, what happened?
>
>   --
>
>     Pete Gontier
>     http://www.m-audio.com/
>
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Midisport and sysex
      • From: Pete Gontier <email@hidden>
  • Prev by Date: Re: Midisport and sysex
  • Next by Date: Re: auval could be more helpful
  • Previous by thread: Re: Midisport and sysex
  • Next by thread: Re: Midisport and sysex
  • Index(es):
    • Date
    • Thread