Hi Fran,
Would be great if you can help to brun the eprom.
Please advise the cost for your service plus airmail to Singapore and i will need 2 of these 1.13 Eprom if possible, Cheers!
Best
Jon
--- In
oberheim@yahoogroups.com
, Narfman96 - Narfland Studio wrote:
>
> Yes you have to have someone make an eprom for you. Or you can buy an eprom burner that can burn (program)Â the older eproms and do it yourself. Look on Ebay for an eprom programmer. They are not very expensive.
> Â
> Then you would need several 27C256 eproms that you can program. Also you need a UVÂ eraser that can erase eproms. They need to be blank so you can program them. These are also available on Ebay.
> Â
> I have one of these programmers and would be happy to make an eprom for anyone that needs one.  Fran
>
>
> >________________________________
> > From: "mudhoney@..."
> >To:
oberheim@yahoogroups.com
> >Sent: Tuesday, February 12, 2013 4:57 PM
> >Subject: [oberheim] Re: Matrix-1000 Updated V1.1.3 firmware for better sysex control.
> >
> >
> >Â
> >
> >How can I upload this in my Matrix
do I have to burn a fisical EPROM with this firmware
If yes How
> >
> >--- In mailto:oberheim%40yahoogroups.com, Martin Ator wrote:
> >>
> >> WOW! this is really cool. Big thanks to all involved :-)
> >>
> >>
> >>
> >>
> >> ________________________________
> >> From: narfman96
> >> To: mailto:oberheim%40yahoogroups.com
> >> Sent: Monday, 11 February 2013, 3:45
> >> Subject: [oberheim] Matrix-1000 Updated V1.1.3 firmware for better sysex control.
> >>
> >>
> >> Ã ‚Â
> >> I uploaded the new firmware bin file. Here is the message I received from Fetz... a big thanks goes out to him!!!
> >>
> >> please find eprom hex file and "instructutions" attached. (I'm not owner of the oberheim firmware copyright nor allowed to distribute that ... but my *small* part is free for use for everyone ... )
> >>
> >> (... its version 1.1.3 just because I had done a 1.1.2 with half the fixes and don't want to mess up my eproms... )
> >>
> >> the "speed up" ist just due to calling some less gigantic engine update subroutine after a VCF change, I haven't found any problems with that.
> >>
> >> *Really* speeding up the matrix or getting the SysEx sounding without artifacts is not possible with the 6809 CPU, it has not enough computing power to do that.
> >>
> >> (In the Andromeda A6 they still have problems with a 50 MHz coldfire (that has 50Mips, compared to the 2Mips here, not to mention the 16/32 Bit Alu ... )
> >>
> >> The trick they use is to build up a kind of "compiled" engine for the patch. The drawback is, that every sys ex changes that, and thus take a very long time. There are 3 (or so) different update functions, one for "calculate whole patch" and others for specialised changes. (I haven't analysed the whole thing, just enough to find the sustain bug ... )
> >>
> >> best regards, Carsten
> >>
> >
> >
> >
>