Sorry for the multiple posts, but I thought of a few more things people may be curious about:

My Matrix 6 code includes the deadband code that was added to V2.13a This code is only
used if it's running on a Matrix 6.

My Matrix 6 code does not support editing the modulation matrix over MIDI. This is somewhat
complicated, and the EPROM is pretty much full.

Q: Will your Matrix 1000 code always update faster than V1.16

A: The V1.16 code does not process every update, as my code does, so if you are updating
a parameter that my code doesn't speed up, then it would be slower than V1.16, but you would
get all of the updates. I tried to hit as many parameters as I could, and also some of the parameters
update very quickly, even in the original code, such as the ones that adjust the envelopes. I didn't
have to touch those.


Bob


--------------------------------------------

On Fri, 9/25/15, Bob Grieb bobgrieb@... [oberheim] < oberheim@yahoogroups.com > wrote:

Subject: [oberheim] Firmware testers sought
To: oberheim@yahoogroups.com
Date: Friday, September 25, 2015, 11:48 AM

Hello Oberheim fans,

    I have been working for quite some time on new
firmware versions for
the Matrix 6/6R and Matrix 1000.

    The only goal was to speed up parameter
changes.     My Matrix 1000
code also includes Gligli's V116 detune code, as this seems
to be a popular
addition.     I also implemented a fix for the NRPN
handling that's a little different
from what Gligli did, but should be equivalent.   I
added a fix for the NRPN inc and
dec functions, as I don't think they would work as
originally implemented.

    Many parameters update much faster in my code
than in the 2.13 Matrix 6
or the 1.13 Matrix 1000.      Unlike Gligli's
version 116, mine processes all MIDI parm
changes.   The speed up is from executing only the code
needed to update the parameter,
not from only doing updates every so
often.      The same technique was used in both
the
M6 and the M1000 new code versions.

    The M6 code has two new SYSEX enable settings
(3 and 4).      3 enables signed
parameter changes, but does not change the parameter values
at all, although they
are checked against the valid range for that parm (which the
orig code didn't do).   Setting
4 allows signed parms as well, but maps them so that a
controller putting out 0-127
values will have the neg values at the bottom, zero in the
middle, and positive values
at the top.      I use this setting with my
PC1600X for testing.

    Anyway, I am currently looking for people who
can get a 27C256 EPROM programmed from a
binary file, and can help me test the new code to make sure
there are no bugs.

    Please email me if you are interested and can
do this.      Of course you need one of these
three units and a way to send it MIDI parm updates.

    Thanks,

       Bob Grieb



------------------------------------
Posted by: Bob Grieb < bobgrieb@... >
------------------------------------


------------------------------------

Yahoo Groups Links


    oberheim-fullfeatured@yahoogroups.com