Hello all, 

short question.. does the midistream API still work in Win XP? 

I wrote an application that uses it and somehow it works on all 
my non-XP workstations and fails on all XP PC's ("device ID out 
of range" or something like that). If it's still supposed to 
work on XP then I'll have to dive into it and find out what I'm 
doing wrong.. Otherwise I'll have to invest my time into finding 
another way to do send a steady flow of midi commands to the 
soundcard (I'd hate to use the windows timer for it *shudders*).

Thanks!

Bram Bos

--

Amsterdam, The Netherlands
http://www.brambos.com

Bram Bos wrote:
> short question.. does the midistream API still work in Win XP? 
> 
> I wrote an application that uses it and somehow it works on all 
> my non-XP workstations and fails on all XP PC's ("device ID out 
> of range" or something like that). If it's still supposed to 
> work on XP then I'll have to dive into it and find out what I'm 
> doing wrong.. Otherwise I'll have to invest my time into finding 
> another way to do send a steady flow of midi commands to the 
> soundcard (I'd hate to use the windows timer for it *shudders*).

according to Jeff Glatt pages this API should still exist in XP:
http://www.borg.com/~jglatt/tech/winapi.htm

Device IDs might have changed in XP e.g. Midimapper (ID was -1) does not 
exist anymore in XP.

G�nter

G�nter Nagler <gnagler@iicm.tu-graz.ac.at> wrote:

> > short question.. does the midistream API still work in Win XP? 
> according to Jeff Glatt pages this API should still exist in XP:
> http://www.borg.com/~jglatt/tech/winapi.htm
> 
> Device IDs might have changed in XP e.g. Midimapper (ID was -1) does not 
> exist anymore in XP.

Thanks G�nter! Apparently it must be something in my code 
that doesn't like XP. I'll check it out..

Bram

On 10 Feb 2004 08:33:01 -0800, bram@mindless.com (Bram Bos) wrote:

>> > short question.. does the midistream API still work in Win XP? 
>> according to Jeff Glatt pages this API should still exist in XP:
>> http://www.borg.com/~jglatt/tech/winapi.htm
>> 
>> Device IDs might have changed in XP e.g. Midimapper (ID was -1) does not 
>> exist anymore in XP.
>
>Thanks G�nter! Apparently it must be something in my code 
>that doesn't like XP. I'll check it out..


I know nothing of this on a technical level.   But on a practical
level - at least one application (Sibelius) has required patching in
order to reliably accept midi input on dual-processor or
hyperthreading systems under XP.   Something to do with corrupt
timestamps.

     CubaseFAQ www.laurencepayne.co.uk/CubaseFAQ.htm
"Possibly the world's least impressive web site": George Perfect

Laurence Payne <l@laurenceDELETEpayne.freeserve.co.uk> wrote:

> >Thanks G�nter! Apparently it must be something in my code 
> >that doesn't like XP. I'll check it out..
> 
> I know nothing of this on a technical level.   But on a practical
> level - at least one application (Sibelius) has required patching in
> order to reliably accept midi input on dual-processor or
> hyperthreading systems under XP.   Something to do with corrupt
> timestamps.

Thanks for the input Laurence. There might be a bug in the XP API then.. 
Though I usually tend to blame my own code and not Microsoft's there used 
to be a bug in the original API as well (the MidiStreamOut Stop-method 
would cause the device to stop and be completely closed in older Windows 
versions). I'll look into it. Maybe there's some more info out there 
somewhere on the net...

It's pretty well known that the MidiStream APIs have never worked properly. 
The raw MIDI APIs are the way to go.



> Laurence Payne <l@laurenceDELETEpayne.freeserve.co.uk> wrote:
> 
> > >Thanks G�nter! Apparently it must be something in my code 
> > >that doesn't like XP. I'll check it out..
> > 
> > I know nothing of this on a technical level.   But on a practical
> > level - at least one application (Sibelius) has required patching in
> > order to reliably accept midi input on dual-processor or
> > hyperthreading systems under XP.   Something to do with corrupt
> > timestamps.
> 
> Thanks for the input Laurence. There might be a bug in the XP API then.. 
> Though I usually tend to blame my own code and not Microsoft's there used 
> to be a bug in the original API as well (the MidiStreamOut Stop-method 
> would cause the device to stop and be completely closed in older Windows 
> versions). I'll look into it. Maybe there's some more info out there 
> somewhere on the net...
> 

-- 
Jim Johnson