Posts by JanosB

+1

Hi everyone,

being an electrical engineer I'd like to design my own IEEE 802.3af mode A compliant PoE injector, which– unlike all ready-to-buy devices I found out there – should accept 9V input voltage so that it could be powered from my pedal power supply.

If my injector should be able to provide the whole 15.4W as the IEEE standard requires, this would require a 9V supply delivering more than 2000mA, which is quite a lot for a pedalboard power supply. However, I wouldn't be surprised if the actual power consumption of the Remote would be a lot lower, this is why I would consider to limit the power that can be delivered to a senseful level.

Now as externally measuring the power consumption of a device powered via PoE is not really trivial, my question is: Has anyone ever used the Remote with a professional PoE switch that monitors power consumption of the devices attached and could give me some more insight regarding the real power consumption of the Remote?

The arduino environment is a great starting point to learn programming! The Arduino framework is written in C++, but as C is a subset of C++, most code lines you see in a usual Arduino sketch are pure C Code.

Did you use the MIDI library by fortySevenEffects for your arduino project? If you didn't, take a look at it. It allows you to attach callback functions for all kinds of incomming MIDI data, which are called automatically if MIDI Data is comming in. You could basically just copy & paste the code above (just remove all the error checking for a first run) into a sysex callback function and do a serial.println(sysExStringBuffer) at the end to see if it works.

Today, I implemented the extended string request with the 32-Bit Controller Number and managed to get the slot names. I'll go on and send some systematic extended string request sequences over the next nights and see if there are any interesting results.

Quote from slateboy

can you show a few examples of what sysex message you send and the sysex message it returns, please?
How are you breaking down the returned sysex into a "usuable" string?

I don't know if you have any experience in C++ programming?

I'm developing the application on my Mac, for that I'm currently developing my own C++ CoreMidi Wrapper - you can find it here and design it around that. Now, if an incoming sysex message arrives, it gets copied into a dedicated byte array and a callback function is called to process the syses Buffer, it basically looks at the 7. byte, the sysex function code and decides how to handle that sysex. In the code snippet below, it simply casts the fields containing the ascii characters of the returned string to char and copies them to a char buffer which can be handled as a standard C-string. That's it

#define SYSEX_FC_STRING_PARAMETER 0x03
#define SYSEX_FC_EXTENDED_STRING_PARAMETER_CHANGE 0x07
switch (sysExBuffer[6]) {
        case SYSEX_FC_STRING_PARAMETER:
            if(waitingForSysExString){
                uint32_t  stringLength=sysExLength-11;
                if(stringLength<=sysExStringBufferSize){
                    uint32_t i;
                    for(i=0; i<stringLength; i++){
                        sysExStringBuffer[i]=(char)sysExBuffer[i+10];
                    }
                    sysExStringBufferSizeError=false;
                    receivedSysExString=true;
                }
                else{
                    sysExStringBufferSizeError=true;
                    receivedSysExString=true;
                }
            }
            break;
        case SYSEX_FC_EXTENDED_STRING_PARAMETER_CHANGE:
            if(waitingForSysExString){
                uint32_t  stringLength=sysExLength-14;
                if(stringLength<=sysExStringBufferSize){
                    uint32_t i;
                    for(i=0; i<stringLength; i++){
                        sysExStringBuffer[i]=(char)sysExBuffer[i+13];
                    }
                    sysExStringBufferSizeError=false;
                    receivedSysExString=true;
                }
                else{
                    sysExStringBufferSizeError=true;
                    receivedSysExString=true;
                }
            }
            break;

If I monitor the MIDI-Data with "MIDI Monitor", a helpful tool for MIDI debugging, while requesting the slot names, it shows me all the messages to and from the amp needed for that:
sysex_log.pdf

Anyway, the my programs string output is a bit better readable It just checks sequentially for sysex string responses on extended string requests over a given 32 Bit Controller Nr range.

Connected to device UM-2
success for Controller Nr 16383: MIDI Controller
success for Controller Nr 16384: MIDI Tests
success for Controller Nr 16385: Rig 1
success for Controller Nr 16386: Rig 2
success for Controller Nr 16387: Rig 3
success for Controller Nr 16388: Rig 4
success for Controller Nr 16389: Rig 5

After continuing to search for a solution, google gave me this post: DIY Pedal board for kemper, I hadn't seen before. This seems to solve my question - I have to send an extended string request . In the other thread, the corresponding 32-Bit Controller Numbes for the slot names are given, so this gives me everything I wanted to get, but anyhow, a list of all possible Controller Numbers and their meanings would be great. Is such a list available? Or should I do a second run with my test code and now poll every possible extended string request (which could take quite a lot of time with 2^32 possible Controller Numbers )?

Okay, as nobody seemed to know anything about that, I took the "hard" way, wrote some lines of C++ Code that sent out every possible SYSEX String Request and wrote the response to a file if there was any. The list generated this way is by far shorter than I expected it to be. I attached it to this post, maybe someone else has a use for that. Seems to me as if I can't request the Information I wanted to get this way

Hi,

I'm developing my own Profiler Remote from scratch. I want it to have 5 little color-displays placed over 5 Footswitches to select the 5 rigs from the current Performance. Each display should show the name of the Rig and should be colored from blue to red depending on the gain of the Rig.

For that I need the controller numbers to create the SYSEX that requests these parameters. I don't find anything about that in the MIDI Parameter Documentation, until now I only found out how to request the name of the active Rig. Before I try out every possible value, can anyone help me with that? Is there an even more detailed list of all controller/parameter numbers that can be requested than the MIDI Parameter Documentation pdf or has anyone done something similar before?