Johey

Did you sort out the problem with your encoders? My MB6582 behaves just like you describe. It usually works pretty good once the encoders have been used for a while, but when the box has been on shelf for some time they are mad. I would believe the encoders are jumpy and that the software should be tweaked to wait longer to confirm a step. Maybe there is a firmware out there with some tweaked settings?

Would you consider selling one case separately?

This is so sweet! I'd love build my next MBSID based on eight psuedovirtual SID chips in an FPGA. I'd keep my MB6582 for reference of course, but a noiseless and potentially bug free version would know its place from time to time.

PCB received a few days ago. Thank you very much! Now it's just about to source the pots. :)

I mean separating the OLED panel from its own PCB, installing some kind of raisers. But I guess there is some kind of leading rubber list in contact with the PCB via some coal layer, and I don't have the equipment nor knowledge modifying that.

Figured it out. :) Before, with the old LCD: After installing OLED: Only problem now is that the OLED display is much thinner than the LCD, hence sinking very deep into the panel. I will try 3d printing some bezel to cover for it to some extent. That's probably what I can do, save trying to raise the OLED panel from the PCB, which would likely fail miserably.

Figured it out. :) Before, with the old LCD: After installing OLED:

SOLVED!!! :D So... I realized the problem was that I had configured the display to be 8 bit instead of four, but the motherboard was wired for four bit connection to the display. Hence, the garbage I saw on the screen was only based on half the data. I patched the four SMD jumpers between the PIC and J15, and now it works perfectly. Sorry TK for bugging you with PM. Please ignore and please forgive. :)

Not receiving a pm from you means all boards are gone?

I thought I'd better downgrade, but I am having a hard time finding the old versions of the hex files. After loads of googling I found MIOS 1.9g and MB SID 2.043. That's pretty close to what I had before, but I had MB SID 2.042. With what I have found so far, I am having no success with my display anyway. It still looks just like on the picture above. Worth mentioning is perhaps the fact that I tried to program a driver for an OLED (device_id_00_lcd7.hex) (have not yet installed the OLED, still using my old LCD), but after that the machine didn't even boot, so that was when I decided to upgrade to the latest and greatest system. Maybe there are some bits and pieces left from that driver in my PIC? Is there any way I can wipe everything in the PIC except for the bootloader to start fresh? Edit: Starting to think the device_id_00_lcd7.hex is the reason. Apparently it is not a driver as I thought, but a setting. So my questions is simply, how can I set it back to what it was? Is there an antidote hex file floating around?

Realized I haven't upgraded my MIOS and MB6582 firmware since I built the box. It was still on MIOS 1.9g and MB SID V2.042. In order to fix what was not broken I decided to have a go, just to end up with garbage on the display. The machine is still responsive and the data on the display is changing in a predictive way. I mean, it is the same each time I boot and it answers in a repeatable way to knob turns and button presses. It feels like it gets the data as before but with a different encoding or something. Any advice on how to fix would be most welcome. :)

I'm just about to try replacing my LCD with an OLED. Just wondering, what do the jumpers on the base board do? Do I need to patch them?

Is there a board left? I'd be happy for one.

Five years have passed since I built my MB6582, so I thought it's about time learning to use it. :-) I have been ripping my hair all day long while playing around with sequencers for basslines and drums. Selecting the sequence from the control surface mod matrix works perfectly fine on SID1, but not on other cores. Going back to the manual once again, I find this explanation: " Due to implementation reasons, the special step display works only when basslines are played on the master core. " What the... Not that I had any hair to rip of in the first place, but... This is just the thing I've been fighting against, I guess? Could anybody please explain to me what the implementation reasons are, and if there is a way to overcome this? Ok, I can trig it using an external keyboard or sequencer, but that is far from convenient. In a performance situation, I'd typically like to manage the bassline and drum sequences from the control surface, leaving the keyboard setup for a lead engine. When talking about sequencers and cores... Is there a way of syncing sequences between the cores? I mean, for instance, if I have a drum sequence running on SID3 and I start a bassline on SID4, the latter should start at step 13 if SID3 is at step 13.

Interested. Sent PM with questions.

https://www.unisystem.pl/en/products/oled/character.html?characters_x_rows=1029 No green ones, unfortunately. One yellow left in stock, after I bought two. White is listed but not in stock. I have received them already, but it will probably take a while before I can try them.

I can't believe it's five years since I built my MB6582. Wow! That means it is just about time for the next Midibox project. This time it will be the SEQ v4. Have had a long discussion with julianf about panel customization. Have ordered the PCB's from Modularaddict and OLED displays from some Polish store I currently cannot remember the name of. As I cannot really find a case I like, I'll try to make my own out of wood. Next up I guess will be an order from Mouser. Happy times! This will be fun. :D

I see. Just one question: Why didn't I think of this myself? :) I can even cut a piece of real glass, dammit! Can even 3d print myself a frame that will hold the glass. That way I could level the glass with the panel.

Anyone who got a spare window for MB6582?

I just discovered the availability of the SEQ4 pcbs today, thinking that... Hey, maybe I should get myself together and build one! Just a few questions... Are there any hard to source components of this build? Is there anywhere to buy aluminium panels or do you need to create it yourself?

I very much like the effort you put into this, C_04! This is needed, indeed. Overflow of MBSID kits is not the kind of problem we suffer. Others, please... This guy is all about to comply to the license as far my eyes reach. Which are your concerns? There are tons of people out there with limited building skills badly wanting an MBSID. sammichSID is perfect by all means, but the production can by far not meet the needs. Besides, we really need an option in Europe without having to pay additional ~40% of the price in shipping+customs. Sign me up for a kit please, if/when it eventually becomes available! I would like to have a 6581 based unit to sing the second voice. :)

Yes, I'm working with the machine this way now. It is good that these things are possible at least, however it gets quite obvious it isn't designed mainly to be used that way. :) But no, I should not complain. I'm very happy I finally made it sound like a C64. :) Next up to learn is the drum engine. At least the patch part. The sequencer is not yet of interest for me as I'm sequencing with a computer, but you never know. Eventually it might be handy.

Yes, I found that one... But do you mean I can use a custom envelope instead of the SID ADSR in some way? Unfortunately it does not seem to work for the multi engine, but it might be a good thing to look at for the lead engine.

The sammichSID boards are quite small already. I doubt it will be easy fitting a modular type of MBSID into the box. But never say never. :) You might ask Wilba if he has a left over kit or if he has any plans of doing another batch. Or of course, asking at the fleemarket if someone has a non-completed kit for sale. Good luck!

Ok folks, this is fantastic! Now I'm actually starting to feel like I'm controlling this thing. :smile: It's all about the multi engine, yes. Thank you peoples! Edit: Oh my gnome! I've just learned about the ADSR bug, the hard way. It's so obvious. Though, I might have overcame it by setting the sustain value to 14 instead of 15. With 15 the bug affects about 1/5 of all notes when going wild over the keys, but with 14 I haven't succeed trigging it even once. It'll eventually bang my head again for sure, but currently I feel it's gone. :D