Re: [prodatum-users] v0.20 "new portmidi inside"

[Jane <rd...@ya...>]

On 10.06.2009, at 06:06, Royce wrote:

> Hi JanE
>
> The good news is that it works with 30ms delay using the BCR as a  
> Midi interface.
>
> It just won't work on either of my MidiSport (2 different drivers)  
> interfaces.
> When using the MidiSport the Rom dialog doesn't appear or flashes  
> briefly, but there is a bit of Midi action for a second or so after  
> the dialog goes.
> Unfortunately the BCR is not my preferred option as I have more than  
> one Emu module.

hmm, it should work with any MIDI interface as far as i can tell. i  
mean, we don't use any commands that are not in the MIDI  
specification...i tried 2 different interfaces: an e-mu usb 1x1 and an  
m-audio 2496. no problems.

> The version of PortMidi I downloaded says that they have been  
> having(had) a bit of trouble with sysex.

i think sysex is not easy to handle because there is all kinds of  
stuff that can happen in the middle of a transfer. but 82 worked fine  
on all 3 platforms for me, so does the new release 131.

> I'd like to get it to work for myself using Borland C++ 5.
> What compiler are you using for Windows?

i am using gcc 4.4.0 in a mingw/msys environment in windows (gcc from  
here http://www.tdragon.net/recentgcc/). and eclipse.

all you need is fltk 1.1.9, portmidi and the prodatum code from svn.
let me know if you need more information.

>
> It is good to be able to use prodatum again.
>
> All the best
> Royce
>
>> greetings (again already),
>>
>> v0.20 has been uploded. it fixes a few smaller issues (setup names  
>> not  being saved between module switching, a MIDI port check on  
>> autoconnect  has been added) but it also features a new portmidi  
>> version (131,  previous was 82).
>>
>> if this still doesnt work for you, install the MIDI drivers for  
>> your  MIDI device (if available). try to avoid the generic windows  
>> MIDI  drivers (even if they seem to work fine).
>>
>> JanE
>>
>