From the original SynthMaker forum (2004–2014), with its members’ names and dates.
oddson ·
OK... so I know the Parser is 'R&D' status but it's seemed pretty stable (if somewhat cryptic) so I'm a little surprised by the following:
It's a hex-parser to extract preset info for an Oberheim Matrix 1000. I'm sure there may be problems with my implementation but the thing I can't figure is why I get two alternating sets of output each time I run it.
Normally I'd try to isolate the behaviour in a simple example but I'm baffled as to where this may be coming from.
(Is there a way to get the parser to step through data?)
exonerate ·
Seems to be the trigger divide your using that is causing it, I can see your adding two strings before the divide so I guess your just wanting only one trigger from that for each add, I don't get the use of the rule sequence, either side of the sequence you are parsing the exact same thing, so it would seem to make the sequence redundant?
I'm not sure what the output is supposed to be but by removing the trigger divide I get @OOBBEEB, and it stays on that.
So I would say it's an error in the implementation or maybe an error with the trigger divide.
Cheers 😉
Exo
oddson ·
I can't test this right now but I think you may be on to something... thanks.
oddson ·
Not a bug...
Thanks exo! I guess a fresh pair of eyes (attached to very smart brain) is just what I needed.
It's clear to me now the trigger divide method is messing up as it's getting an odd number of triggers each time. So it reads a zero as the upper nibble even when it's not. But since it is on so much of the data I convinced myself it was reading the bulk of the data correctly and so the problem must be more sporadic.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker