@ddw_music said:

If it's only an ID (and you won't be doing math on it), then you can safely represent them as 4 bytes, or 2 16-bit words, or whatever. It would get more difficult if it were, "after reassembling the integer, I need to multiply by 5 and subtract 7" but if you're not doing that, then it should be OK to just continue with the present approach.

Thats what I thought as well.

After some messy patching with execution order issues, this is seems to do the trick:
[expr int(($f1 & 15)*16 + ($f2 >> 3));
int(($f2 & 7)*32 + ($f3 >>2));
int(($f3 & 3)*64 + ($f4 >>1));
int(($f4 & 1)*128 + $f5]

Not yet tested with real midi messeges, but I am confident.
cheers

@ddw_music said:

@bang Are you using a version of Pd compiled for 64-bit floats?

I don't know. How can i find out? I am using PD on different devices/OSes. The current Projekt should run on RaspberryPIOS 32bit, so PD's float is probably 32 bit as well? Shifting the upper 8bits [>> 24] (for 32bit into 5 bytes/7bit tranlation) could be an Issue ...?

How will these 32-bit integers be used, btw? Depending on the usage, you might be able to live with a pair of 16-bit words.

Well, the device (Kemper) I am trying to communicate with, sends/receives these values in MIDI Sysex packages. Some parameter can be accessed by these 32bit addresses, but some are undocumented. So, let's see where this leads.

Or, use Max/MSP or SuperCollider, both of which have a signed 32-bit integer datatype.>

I started prototyping this in PD cause I am kinda familiar doing midithings in PD.
Maybe I move it to python later on (learning it right now).

btw: bitshifting is developing quite well
Thankx again

Nice suggestions!
I will dig into it soon.
cheers

Hi, I am looking for a way to decode 4bytes/32bit encoded in 5 bytes extracted from midisysex.
They look like this:
0---1111 | 01111111 | 01111111 | 01111111 | 01111111 (where --- are unused and all 0 need to be cut off)
or in other words:
0 - - - a7 a6 a5 a4 | 00 a3 a2 a1 a0 b7 b6 b5 | 00 b4 b3 b2 b1 b0 c7 c6 | 00 c5 c4 c3 c2 c1 c0 d7 | 00 d6 d5 d4 d3 d2 d1 d0
should become:
a7 a6 a5 a4 a3 a2 a1 a0 | b7 b6 b5 b4 b3 b2 b1 b0 | c7 c6 c5 c4 c3 c2 c1 c0 | d7 d6 d5 d4 d3 d2 d1 d0
How could this be done? I am not a bitshifter guy yet.
my attempts have failed miserably so far.
cheers

@ddw_music said:

@whale-av said:

@bang Pretty sure mommuplat will only use vanilla objects.
[sysexin] and [sysexout] are vanilla.

[sysexout] isn't.
Anyway, I moved to pd on a Raspberry.

I did a few more tests: [sysexin] and [midirealtimein] still don't work on mobmuplat.
[midiin] does! But it suppresses the startbyte 240(f0) and stopbyte 247(f7).
So let's see if I can deal with that.

Thanks for your input

Hi, sysexin does not seem to work on Mobmuplat, at least not on my devices.
can anyone confirm this?

@svanya said:

@bang Cool. I'd love to see it. Can you share it here? Thanks.

I didn't find it yet, sorry! Patched it in the old "extented" days.
I am a bit buisy, I will look in a week or so.

I did a similar thing once, with a longbang in addition. A double-long-click is maybe an other option (to confuse the user ).

I see, thanks for clarification.
Dirk