Whichever system you try, it might be safe to create a function that can
be called for sending a MIDI message, indirectly calling the one
supplied by the package. This will make things easier in case the
package is changed…
Bernard
Anthony Kozar wrote on 23/08/2020 23:05:
> Midishare (from Grame) is still around. A new package for OS X El
> Capitan was posted about two years ago. It is not clear to me whether
> this package has any code changes compared to the previous release for
> Mac OS X but the libraries in it are Universal binaries for i386 and
> x86_64. While there has been activity in the Git repository as recent
> as 2016, the last Windows and Linux releases appear to be from 2013
> and 2006 respectively.
>
> http://midishare.sourceforge.net/
>
> The JACK Audio Connection Kit is cross-platform and appears to have
> some support for real-time MIDI even though it is primarily a tool for
> routing audio signals. The JACK project appears to be pretty active.
>
> https://jackaudio.org/
>
> Overall, I am guessing that PortMidi will be the easiest to distribute
> with BP so that BP users don't have to install anything extra. But
> I'm really not that familiar with any of these libraries.
>
> Anthony
>
>
> On 8/19/20, 11:20 PM, Bernard Bel wrote:
>> It has a drawback: "RtMidi does not provide timing functionality (i.e.,
>> output messages are sent immediately)."
>>
>> In the tutorial (http://www.music.mcgill.ca/~gary/rtmidi/), time spacing
>> between events is created by a "sleep" function which is
>> platform-dependent. My objection is that it will cumulate errors.
>> However, developers might have found tricks to avoid error cumulation —
>> unless they estimate that it is not so important.
>>
>> One of the reasons for insisting on time accuracy is that several BPs
>> improvizing together would need to stay perfectly synchronized (without
>> sending specific MIDI messages for their synchonization).
>>
>> Bernard
>>
>>
>> Rainer Schuetz wrote on 20/08/2020 00:36:
>>> You might want to have a look at RtMidi for comparison:
>>>
>>> https://github.com/thestk/rtmidi
>>>
>>> There are Portaudio and Portmidi, and RtAudio and RtMidi… The later
>>> seem
>>> to be a result of some lack of responsiveness of the team behind the
>>> “portXYs”. I can’t make a judgement at all but I know that projects
>>> that
>>> still have a choice, tend to prefer the RtXY’s for the community
>>> responsiveness, and the codebase is much more recent.
>>>
>>> Best
>>> .r.
>
>
>
> _______________________________________________
> bolprocessor-devel mailing list
> bol...@li...
> https://lists.sourceforge.net/lists/listinfo/bolprocessor-devel
|