rutgerv

Yes it does! Good point. You need at least RC19, but preferably the latest. From that version on the communication between Editor and MBSID is different. Best, Rutger

Hi everyone, happy you guys like it! I hope it speeds up the process of building patches and also allows for easy exchange of patches between users. There may still be some bugs in it, so please report them. Also, I have some extra features in mind that will be added in the future. A special note to Mac users: the part of Java that drives the midi interface is not capable of handling USB devices or other plug-and-play things correctly, therefore it's recommended to install the so called 'mmj' Java extension (http://www.humatic.de/htools/mmj.htm) if you are experiencing problems with your midi device being recognized by the program. Best, Rutger

Wow, great! It's released ;). Thanx, TK! Rutger ps. Wow, I'm surprised about the screenshots. It looks totally different on a Mac!

Yes! I'm currently finishing the beta version of the new MBSID V2 Editor. It will contain a librarian to send, receive and organize patches and banks on the MBSID V2 and it will contain an editor for every engine (Lead, Bassline, Drums, Multi). I already let TK take a look at it and he had some good suggestions, which I'm going to take into account (mostly) before I release a beta version. With it I'll probably also include some nice new patches for the MBSID V2 and since the editor allows us to create patches and exchange them really easily maybe we can put up a 'patch exchange' forum, or is there already such a thing? Greetings, Rutger

Hi! are you using V2 of the SID firmware? In that case it's slightly different from what's described on the wiki I think. The code I downloaded from www.ucapps.de already had a line in it for the detention mode. It looked like this (just search on these lines in the editor...): ENC_ENTRY 1, 0, MIOS_ENC_MODE_DETENTED2 ; menu encoder For the bourns encoder I changed it to ENC_ENTRY 1, 0, MIOS_ENC_MODE_DETENTED3 ; menu encoder which works perfectly for me! Rutger

chips sold!

That's about the same cost as my MBSID V2 with 8 SID's and 8 Moog filters in a rack with a control surface!

To begin with: Chewi81, you have new email! And furthermore: Wow! Haven't checked this thread for a couple of days. Anyway, as several people already said, I have no reason to think that Chewi81 is going to use the SID's for a different purpose than building him(her?) self a midibox SID V2. @ Chewi81: you probably don't understand what the fuzz is all about, but there was some guy making midiboxes and selling them on ebay (and making profit), which is not allowed since Thorsten (=TK), the guy who created this project and put it all on the internet for free (!!!!) is the only one who has the rights to do this. The midibox stuff is still his 'intellectual property". So MidiBoxes are just for home building and using yourself and not selling to make profit. Rutger ps. Guys: can be please get back to what this thread was supposed to be!

Hi, sorry, I think I also told you over the email: that's really too much work for me to record that! I don't have the chips sitting in the synth anymore and swapping them (including the caps) takes alot of time. However, I think there are many demo's of 6581's playing basslines and other stuff. UPDATE: 2 chips have been sold. These are still left: - MOS 6581 0184 (1x) - MOS 6581 0484 (1x) - MOS 6581 0883 (1x) - MOS 6581 2282 (1x) - MOS 6581 CBM 3384 (2x) - MOS 6581R4AR 1187 14 (1x) - MOS 6581R4AR 0487 14 (1x) Greetings, Rutger

Let's make those SID chips 12,50 each!

Maybe it makes more sense to extend the maximum of 4 cores (1 master and 3 slaves) to 6 cores and have a 6-voice true stereo synth using just the Lead engine. That is...if you really need more than 4 voices. Many great polysynths work with only 6 voices or some even with only 5 (Prophet). Having it true-stereo is a big plus for me! And for my use 4-voices is really enough. I already have other synths to do the big poly stuff, the power of the MBSID V2 is mostly in the stereo option and the complex modulation options I think. It reminds me alot of my Ensoniq ESQ1, since this synth is also very over-engineered (in a good way) in the modulation section (lots of LFO's and EG's). Greetings, Rutger

That would be me ;)

Hi, I'm selling 8 SID chips of the type 6581 (all tested and working) at 12,50 euro's each plus shipping (from The Netherlands). The exact descriptions on the top of the chips say: - MOS 6581 0184 (1x) - MOS 6581 0484 (1x) - MOS 6581 0883 (1x) - MOS 6581 2282 (1x) - MOS 6581 CBM 3384 (2x) - MOS 6581R4AR 1187 14 (1x) - MOS 6581R4AR 0487 14 (1x) I also have some Styroflex caps left. They were bought new this summer but have been used for testing, so the leads are already cut off very short. Since I know they're hard to get and since I'm not using them I offer them here. I have 8 pcs of the Styroflex 6.8N type (see Reichelt website, where I ordered them) and 6 pcs of the Styroflex 470P type. Please send me a private message if you're interested. Kind regards, Rutger

Hi TK, thank you very much for fixing the SuperPoly voice behaviour (the reset on patch change)! This is really nice for me since I use the MBSID V2 for live purposes and notes getting stuck or not playing is a very big issue then. Maybe there's another thing that could be improved, but it's up to you if you find it usefull. It has to do with the behaviour of the portamento. Most modern synths I've played reset the portamento between patches and ignore the portamento of the first note played on the new patch. This is usefull for smooth patch changes during gigs. At the current version of the MBSID V2 software the portamento resets to notes number 0 and each first note played after a patch changes sweeps the pitch from this lowest note up the note that is played. This can be a problem when switching to a lead sound with long portamento in a live situation... I would propose to ignore the portamento of the first note played after a patch change. It's up to you of course if it's worth spending on (I can live with it the way it is :) ). Rutger ps. I already mentioned in another thread, but maybe this is a better place: the V2 editor is progressing very well and I expect to have a beta version finished in a couple of weeks.

Hi, maybe it's just nice to mention that I'm working on a software editor for the MBSID V2. I've completed the Lead-engine editor and I'm working on a patch management system now. A beta version will be released in a couple of weeks. Greetings, Rutger

Wow, I really like the direction in which the MBSID V2 firmware is progressing. Every few months a stupid and insane idea crosses my mind: building a digitally controlled modular synthesizer that is entirely controlled from a (slightly modified) MBSID V2 engine. Reading this reminds me again of this plan, however it just seems to expensive and it will take an insane amount of time to design. I imagine something looking like a Nord Modular G2, with a software tool that enables the user to route individual modules to other modules. However, the signal paths stays analog! There would be a main board with a master controller (or multiple) and several slots that voice cards can be put in and a couple of FX expansion slots to hold Flangers, Phaser, Filters, etc. The synth would also include a giant switch matrix controlled by a PIC to enable all possible routings between modules. The biggest problems: - keeping the VCO's in tune (maybe some sort of autotune circuit can be used) ! - keeping up the signal quality with all routing options (i.e. a very decent switch matrix should be used!) - keeping down the costs Maybe if TK, Wilba and I retire and we hook up with Tony Allgood (Oakley modular synths) we could build something like this ;). Rutger ps. Hehe, sorry for sharing such crazy thoughts!

Wow, that's a nice spectrum of something between white and pink noise! A question that comes to mind is: how loud is the noise? If there's a broken connection in the audio-path and you crank up the volume you can always generate noise of this type, but if this noise is really loud (the same loudness of a SID output) then something else is actively producing this noise. A couple of things come to mind: - Check if the problem isn't coming from a dirty power rail. If something got damaged due to the sparks and smoke you should be able to see this with your scope. An unstable power supply could cause this noise. - Transistor T1 could be damaged due to voltage peaks when the sparks and smoke were going on - Transistor T1 could be pin swapped Greetings, Rutger

Problem solved! 8) When I swapped the PIC's I found out that 2 of them were still running on MIOS 1.9e. I uploaded the latest MIOS to all of the cores a couple of months ago, assuming that it would succeed as it did with uploading the SID V2 application without feedback. Appearently it did not :). So I did it today and everything seems to work fine now! Rutger ps. Just a little note on the current 4-voice polyphony option: it seems that the voice-handler doesn't reset on patch change. When I change patches while holding a note the oscillators used at that time become silent when they're called in the next patch.

Hi guys and girls, I'm having problems with my MBSID V2 and I'm not sure if it's related to hardware or software. Maybe somebody knows? I've just updated to MBSID V2 RC14 and also uploaded the new patches. My setup consists of 4 cores with 8 SID's (6 of them are 6582's and 2 of them 8085's). The first core is the master and has the CS attached to it. The problem I'm experiencing is that the patches played on core 3 and 4 sound differently because the ARP and WT are not working. Patches that don't use these features sound alright, but when a patches uses an ARP or WT it only plays the notes played directly (without the option WT only on). So, nothing is coming from the ARP or WT path. I have the feeling that it has to do with the ARP and WT not receiving a clock signal, so I was wondering how this is generated. I can confirm that all cores are running and are set to the same parameters in the Ensemble setup with the only difference that the Master core has the CLK set to Mst. and the other 3 cores have it set to Auto. The CAN-bus also seems to be working and the patches are loaded from the same bankstick. What could cause core 3 and 4 to go wrong and 1 and specially 2 (which has the exact same configuration) to work alright? Kind regards, Rutger ps. One of the assumptions I have about this is that 3 and 4 are running on an older version of the firmware. Could this result in the problem I'm having? And is there a way to check the firmware of slave cores? I've uploaded the firmware to each core individually, but the uploading to cores 2,3 and 4 has been done in the "manual" setting, while core 1 had the ability to provide feedback for the upload process. I also tried to hold down "menu" while booting, and nothing happend, unless it happened so fast that I didn't even see (does it take less then 0.5 seconds to clone to all slaves?).

There are many good schematics for bi-polar power supplies on the net. The 7812 regulator is designed to deliver a positive 12V DC, but there's also a 7912, which delivers a negative 12V DC. A combination of those should be able to give you the voltage you need. However, it's not that simple. Besides this voltage regulation you may also need more capacitors in the circuit for decoupling. Greetings, Rutger

Hi, I'm not sure if I can help, because it's hard to understand your exact configuration, but I'll give it a try. Some ideas: - Check and double check the wiring of the PSU. Is there a chance you have swapped a supply wire with a ground wire? - Check for any broken contacts in the audio path (from SID audio out to you jack socket). If there's a bad contact between the SID and your audio output you would end up having a 'loose wire' which can acts as an antenna for noise. It's similar to the noise that you get when you pull the cable out of a guitar and leave the amp on. Let me know if this helps. Greetings, Rutger

Very cool t_xen! I'm curious how it sounds! You can probably make the resonance controllable over CV too with half a 13700. You can put the 13700 in a VCA-configuration and use the VCA to control the feedback path. I did the same thing with the Rick Jansen Moog schematic and it works great. Greetings, Rutger

Hi TK, wow, this SysEx implementation in the new version is great! The features and documentation are really helpful for developing the MBSID V2 editor. Just a quick question by the way: can I use program changes and bank changes to select ensembles? Or can program changes only be used to select programs? Greetings, Rutger

When the SID V2 is out of bugs, maybe you can start debugging some Microsoft stuff ;).

Wow, again: deeply impressed! Thank you very much for the sustain fix, TK. It's something I use really often, so it's cool to have it working smoothly. I think the MBSID V2 is getting near the point where all regular synth manufacturers should start eating their harts out because of the cool stuff they do not have inside their synths! Greetings, Rutger