I suppose trying to use the latest version of RtMidi would require more
work than simply address the issue I've reported.
But, we could at least fix the problem on Linux where you cannot send 1
and 2 bytes messages (program changes, real-time and aftertouch), that
seems a big one to me.
According to the headers, ChucK uses RtMidi Version 1.0.4 from 14 October
2005.
On Fri, Jul 5, 2019 at 10:10 AM Forrest Cahoon
wrote:
> Have you grabbed the latest rtmidi sources from
> https://github.com/thestk/rtmidi ?
>
> I briefly looked for the code you reported changing and didn't see
>
Have you grabbed the latest rtmidi sources from
https://github.com/thestk/rtmidi ?
I briefly looked for the code you reported changing and didn't see anything
that looked like that in HEAD.
On Wed, Jul 3, 2019 at 3:22 PM mario buoninfante <
mario.buoninfa...@gmail.com> wrote:
> I've found a
I've found a workaround (not sure it's a proper one though!)
more info here: https://github.com/ccrma/chuck/issues/130
this now allows to send SysEx from Linux as well :)
On 02/07/2019 22:15, Michael Heuer wrote:
Great, thanks! I'll start a new thread asking how best to use it!
michael
just found out on Linux I cannot send anything that's not 3 bytes!
No Program Change, no Aftertouch, no Real Time.
I can receive them (real-time included), but I cannot send them since I
get this error:
[chuck](via RtMidi): RtMidiOut::sendMessage: event parsing error!
Cheers,
Mario
On
I'd say go for it! It would be nice to have proper SysEx and MIDI clock
support in ChucK.
I recall there was some progress on the latter; did I read somewhere that clock
messages are available via RtMidi but simply disabled in ChucK for performance
reasons?
michael
> On Jul 2, 2019, at
Hi everybody,
One month ago I got started with an Open Source project whose goal is to
support some hardware on various platforms/environments/programming
languages (Pd, SC, Processing, Lua, Python, JS, etc.) and of course my goal
is to have ChucK on board as well (hopefully I'll share more info
