EventGhost

Hello mparadiso...

Sorry about the late reply, I have been busy with some plugin documentation, and I was also a little ill recently.

I am not familiar with the Amulet remote control, but the two receivers from the Internet are familiar.

You might want to look at the Remote Controls topic first ...

smprather...

Check out the Remote Controls topic.

I think you might have a 0005 or 0006 or 0007 or 0008 remote, which means you are using the wrong plugin for it.

WharfRat...

The Remote Controls topic might be useful...

Did you try to see what codes you get with Advanced USB Port Monitor for the Volume and Power buttons?

Sorry, I did not mean that you should try using the PHX01RN plugin with your remote.

What I meant was that you can try to create a plugin by using another remote plugin as an example.

I was not aware that your remote uses a DLL as well.

Are you sure that your remote does not work with the MCE ...

Yes ...

I created (actually, fixed) the PHX01RN plugin by using Advanced USB Port Monitor.

So, use that, and the source for the PHX01RN (now fixed in the newer EventGhost releases), or other WinUSB remote, as an example.

Perhaps you need to see viewtopic.php?f=2&t=6063

THANK YOU, THANK YOU, THANK YOU...

Simple?
Yes, but only after I studied it carefully...
I would never have arrived at your solution.
It is exactly what I wanted to achieve, and has tested correctly as well.
Thanks again...

Pako...

Sorry, it took me a while to create a code snippet for you.
__init__.py
I had to change the example to a MIDI Output Device.
Not everyone has MIDI input devices.
All motherboards have MIDI output devices.

It is as simple as I can make it for our purpose.
When the Open Device macro is ...

Well, I struggled with using self as a parameter for dwInstance , and I couldn't get it to work.

Then I went back to Luse's Learning Python 5th Edition book.
Found something about function attributes on page 564.

This is what I do now:

import eg

eg.RegisterPlugin()

from ctypes import *
from ...

Aah, thanks for the quick reply Pako...

I think I have solved it.
Currently I did not use the dwInstance parameter of the callback for anything, but I think I can pass self as the parameter for that, so that it will be accessible within the callback.
I hope that self is just a pointer, and not a ...

Perhaps I need to ask a different question in order to accomplish what I need...

How can I access self from within MidiInput.Callback, which is actually MidiInputCallback after self.Callback = MIDIINPUTCALLBACK(MidiInputCallback)?

I hope what I am trying to achieve makes sense to you...

I am writing a MIDI plugin.

The Windows Multimedia API sends messages to a callback function.

Currently, my callback function is implemented as a standalone function:

import eg

eg.RegisterPlugin()

from ctypes import *
from ctypes.wintypes import *

# define the prototype for the MIDI Input ...

Thanks Pako...

I just realized that it was a stupid question.

MIDI data is transmitted serially, so we only need to deal with it one byte at a time.
But it is nice to know that there is no particular limit to payload sizes.

I should think harder before I open my big mouth...

Check out Techniques: controlling multiple programs...

Hi...

I am writing a new plugin (for MIDI devices).

Some of the events will have a payload, which could conceivably be quite large, like many kilobytes.
For instance, MIDI System Exclusive messages can contain audio data samples for instruments, and so on...

Are there any payload limitations that ...