Dave Strength

The CEM reaplcement is another good idea...but that one's a bit easier since the original interface to that chip was in fact all analog. The SID is a bit different since it's interface is digital...an 8 bit data line and 4 bit address line. I was really looking for some guidance from the programmers as to which approach might be best: the stand alone micro interface...or integrating into the current MDSID code. Perhaps even V3 accounts for this and a full external interface is allready planned? After all, sooner or later all the SIDs will be gone. I can't really find any now. As far as the CV outs, I'm assuming we can use the existing MIOS functions for driving the AOUTs (NG's). The envelopes pose a bit of problem since they are CV intensive. For a true SID replacement...I'd probably just handle those digitally inside the micro and output one CV per VCA. So with three OSC Pitch and PW, Filter Freq and Res, and three VCAs, that's 11 CV's per SID interface. I'm curious how many AOUT's a single MBox core can drive? Is it 32?

Like someone mentioned below, I too am very impressed with the SID synth engine. I've been building analog synths for a while, and I came accross MIDIBox for the MBCV interface. After building it, I was interested in expanding the polyphonic functionality...and noticed comments in the ASM that eluded to making things more like the MBSID. After reviewing the SID I was blown away by the concept and implementation. So I'd like to explore the options of adapting the MBSID engine to a complete analog synth. The concept here being able to not only take adavantage of the modulation subsystem...but also of the patching and overall synth management functions. I realize there are quite a few external interface options allready present...but I'd like to have more flexibility and control over the synthesis portion..ie...some freedom from the SID chip will style enjoying the awesome MBSID engine. Two possibilities come to mind. The first would be to develop a comm interface (perhaps PIC) to emulate the SID...essentially converting the SID control data back out to analog CV's and digital CMOS switches. This would have the advantage of being compatable with future MBSID releases...i.e leaving the original MBSID code unmodified. The second, would be some modification of the MBSID itself to support more AOUTs and DOUTs to drive the analog synth. Regardless of the method, the analog synth itself would be modeled after the internal SID block (or more precisely after the SID interface): 3 OSCs with TRI,SAW,SQR, and NOISE waves/ Pitch and PW CV, 3 VCAs with CV, 3 ADSRs with full CV, and Multimode Filter with Cutoff and Res CVs. I searched the forums and didn't find anything similar...so I apologize in advance if this has allready been covered. I'd greatly appreciate and input, ideas, or advice. Thanks, Dave Strength

Figured it out...had a short in the midi cable. MIOS still allowed the upload..though it was very slow, it reported successful. Changed out midi cables, got a good reliable core status check, re-uploaded and everything worked. Thanks again.

Thanks for the ideas. Indeed I built a new hex file (having deleted the old ones just to make sure) and loaded it via MIOS studio. I performed the test you described in shorting pins 4 and 5 to ground, however this did not produce any results. I think the DIN is working ok since the LCD readoutresponsed to Select and Exit buttons correctly. Also, I think if the changes hadn't been made to the hex file, the Select and Exit functions would be assigned to different pins....as it is now, they are working propely on pins 6 and 7. I've tried changing the IC's on the DIN, changing the encoder defintion,etc. I've confirmed the wiring on the encoder, and ohmed out the encoder with no wires attached. Is there anything else you think I might check?

I"m having trouble getting the encoder data wheel to work on my midibox CV. I'm using a Bourns PEC16-4220F-S0024 24 2 bit gray code encoder. I've rebuilt and downloaded the application with the changes to setup_j5_enabled.asm including defining the line #define DEFAULT_ENC_DATAWHEEL 0. (Initially i had defined it as 1, but changed to 0). And, I've confirmed the encoder is defined in mios_tables.inc. The Select and Exit buttons work correctly, so I'm guessing that the DINX4 and CORE is working properly. But, I get no repsonse when jogging the wheel. This is my first midibox project so I'm somewhat lost here. Any help would be appreciated.

I'm still building my Midibox CV, and I have some questions concerning the poly mode. What I'd like to do is set it up for a 4 voice poly mode, where CV's 1-4 are for the notes of voices 1-4, and CV's 5-8 are for the velocities of voices 1-4. Is there a way to set this up? Thanks in advance. Dave