• oid

    That was the problem, all is well and the data is filling the array exactly as expected. Regarding the sysex, this message is a single complete sound, each number between F0 and F7 is a parameter in the synth and indexed just as the array is, 1 is VCO1 Octave, 2 is VCO1 semitone, 3 is VCO1 detune and so on, so the plan is just to set the receive symbol on a [nbx] to correspond to its parameters spot in the array, n1, n2, n3, etc, then the counter stepping [get array] and [pack] to get the full symbol and data for [send] to send off to the [nbx]s, seems simple. The data sent to the synth will be as CCs and short single parameter sysex messages, parsing the full sysex for the sound just seems so much more sensible than sending 350 or so individual sysex parameter requests.

    7F is just every parameter I have set at full in that patch :) A few Dozen of the 00s are reserved bits used internally within the synth though, it is not quite all fun stuff.

    Thanks for your help!

    posted in technical issues read more
  • oid

    back to gibberish output, my changing [f] to [i] had caused it to count, turning it back to [f] reverted it back to much the same as column 3. Why the difference between float and integer here?

    posted in technical issues read more
  • oid

    @whale-av, Here you go.
    dumps
    first column is the hex patch dump right to amidi and is 100% confirmed correct, second column is the output of [print], third column is the array and the fourth column is also the array, not sure what happened there but it seems to be counting instead of gibberish now. Might just be my tired eyes missing something in the patch, here is the patch.
    sysex.png

    posted in technical issues read more
  • oid

    Hello, I have been working with making an editor for a synth and am having some issues. I am doing a program dump of the synths working sound to populate the number boxes with the correct values, [sysexin] seems to be working for that and when connected to [print], every thing comes out neatly on the console, 382 separate prints each with one parameter. So I connected [sysexin]to a [tabwrite] and a counter to step the index of tabwrite, standard [f] and [+] counter. This does not work, data is coming through incorrect and it only steps through 247 of the arrays index, results are almost consistent, but there are some differences between dumps., generally an impossible number or two well beyond what two digit hex can represent. Running on linux and pd 49.

    Any ideas as to what I am doing wrong, or better way to accomplish what I am attempting?

    Edit: Forgot I just updated, running pd 50.2

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!