Blofeld Sysexdump into Max
Hi, i´m having a hard time with my Blofeld, Max and Sysex.
I got the basic Communication via Sysex including Parameter feedback done but would like to use a Sounddump from the Blofeld to set my Controllers Dials according to the current active settings on the Synth.
I use Lobjects for capturing the Dump but it´s not nearly as big as it should be (392 Bytes)
here´s what i got, thanks to Peter Elsaer´s Max&Sysex.pdf
Any help would be so much apprechiated, thanks!
This thread may help, although there's nothing about Lobjects in it: https://cycling74.com/forums/capturing-sysex-dump
Thank you, i know this thread and actually used the snippet you posted but for some reason the dump i receive is not long enough and i don´t see why. Regardless if i use your code or if i try it with Lobjects.
So the sys-ex dump Max gets from the Blofeld doesn't have everything in it that you need?
Or does the Blofeld send it all but Max doesn't manage to store all of it?
The Blofeld does send all, i recorded a dump with Sysex Librarian and everything is as expected.
It´s Max that doesn´t store all of it and i don´t know why. I´ve set the capture object to 4000 and more which should be plenty.
The Yamaha VL70 sends a single patch dump as 2 sys-ex messages. I wonder if the Blofeld does something like that and can't be handled by your current Max patch?
(A clutching-at-straws thing to try might be my snippet from that other thread but with the zl length set to 32676.)
Thanks but unfortunately it doesn’t work. It seems like i‘m missing the header of the dump and a lot of the Parameters but the the dump starts and ends correctly with F0 /F7, this is weird.
FWIW you are clearing your capture every time you receive a chunk "and or" your chunk size is only 255
thanks, unfortunately this didn´t work better.
I made a sysex dump to sysex librarian and marked how much of the dump i actually receive, everything above and including the blue stripe is received in Max, the rest is missing.
Does zl Group or capture not have enough space to receive 392 bytes?
Also, why do i get the F7 close message if i don´t get to the end of the sysex dump?
Mysterious :)
In your OP patch only the blue line down to F7 are there, what changed?
That's bizarre! You're getting the first 256 bytes, which is the default length of zl objects.
I just had a play with that snippet and there's something odd going on with... don't know... maybe [zl group]?
In your OP patch only the blue line down to F7 are there, what changed?
-
I changed the patch and at least got the header
In his Max&sysex pdf for LobjectsPeter writes:
This (Lchunk?) works for messages up to 255 bytes. If you expect bigger ones, or multi part data dumps, you need to use Ldumpster.
Since the dump is bigger than 255bytes i tried Ldumpster but couldn´t get it to work, so i tried another approach, found somewhere here on this forum, as seen in the patch,
Bill, i tried your patch and now i am even more confused.
The dump using your patch know shows 392, which is what i want, right?
However, if i use one of your testfields to convert this very dump converted to hex (using lhex) it´s all of a sudden 256 length.
Yeah Martin, there's something weird going on that I don't understand, and it seems to be about list lengths. So does your problem. Maybe they both have the same mysterious cause? I have no idea why the 136 from [zl len] isn't 256, and it's just as wrong with other test dumps i've tried.
BTW, if Lchunk has a maximum length of 255 is Lhex the same?
(Unfortunately I haven't got time to have more of a play with it for another day or so.)
Please look at the last tab in the zl help file. You need to increase the @zlmaxsize . Note - the zl.len will report 256 even if the list is longer unless you increase the @zlmaxsize length.
Thanks a lot, it seems to work now. As far as i can tell the Lhex object has a maximum of 255, that added to my confusion. Thanks everyone, i think i got it.