kokoon

interesting idea - 1 row down = 2 semitones up

that's great! i'll try this and see if it helps me creating new patches. why is it that you say that we need a bankstick for all this?

here's a few things (i'm sure this is all written all over the place but anyway) - if i wrote something wrong, please someone correct me: a few basics: * .hex file is the "machine code" that needs to be programmed into the PIC. it's often called "binary" or "compiled" or "assembled", ... it's not readable for humans. * you get the .hex file after compiling/assembling the .c or .asm files. you generaly don't need to do that because you already get to download the binaries. * you upload the .hex files into PIC via MIOS studio. * if you have troubles running mios studio (i have) you can convert the .hex files into sysex files (.syx). sysex is an extension of midi and can thus be uploaded to the PIC with some midi tool, for example MIDI-OX. MIDIBOX: * all the code is in the core module's PIC. there are 3 "layers" of code. - 1. layer is "bootloader" or "bootstrap" and is only used when the machine is starting (and for uploading binaries?). you can upload this only with a PIC burner. usually people order PIC chips from smash or joerg and have them the bootloader already burnt for them. - 2. layer is MIOS. it's the operating system, like windows. it offers an API (a set of functions) that the APPLICATIONS use. you can upload the MIOS binary (.hex) as described above in the first 4 points. note that you can only upload MIOS in the first 2 seconds (i think it's 2) after the bootloader is ran (that means after you power-on the core). when you upload MIOS all that you had in the PIC (except the bootloader) is lost. more specifically - previous MIOS and the applications are lost. that means that you don't have to "erase" it when let's say you upgrade the MIOS but instead you just upload it. and then the application too. - 3. layer is APPLICATION. there are various applications for various midiboxes. you'll need the MBSID application. you can upload the application anytime the core is running. the previous applications are lost. so when upgrading you don't need to erase first. the applications are binaries just like the MIOS and you upload them the same way. the document i learnt all this from is http://ucapps.de/mios_bootstrap.html don't let the "Device ID" discussions confuse you for now. for start you just get single CORE+SID to work. the display component of the device id is probably okay the way it is by default.

jar is just a zip file renamed.

well the filter is more "filter" (still pretty poor for a 2-pole filter) but it's also got the problems with steppiness. i'm building mine with 2+2 configuration i think that's the best.

yay it's fixed now. i wired the clock from the core instead of the crystal. like you said. problem solved :D

heh you're right i just have to measure them :) how much bigger fuse do you think i could stuff in the C64 psu without damaging it?

ahh so that's probably also why you didnt make sustain available as the modulation target (in the mod matrix) ;) it's a shame though cause every time the gate is triggered the VCA punches with the max volume first and you can hear that. so the workaround with WTing the note triggers and then setting the sustain for each one (very fast) won't work. maybe something can be done with the attack hmm... any idea how to make a channel quieter?

i'm glad you like the patches. i can make many more. a question - i found the patches work (sound) alot better if you stop the ocillators with the WT when the sound should stop. is that an okay thing to do? i mean do others (you?) do that in your patches? regarding the filters - i could really use the HP and BP filter to improve the high hats but those filters applied to any other patch would worsten it quite a bit. do you think it's still okay to use such specific filters? i mean if someone will then turn on the filter for the bassdrum it will sound really bad. when the patches use no filters at all you can still put all 3 channels through a filter for "equalizing" purpuses but not if the filters are specifically defined for a patch. do you know what i mean? i'm just wondering what would be best. then another question about the WTs - i'm not completely sure how they work but is this normal: if i set an absolute value in one WT step then i can't set it any lower in any of the next steps. i haven't experimented much with this specific case but what i did - i was trying to alternate the OSC1 sustain level between two values (lets say 63 and 31 but when it hits the first value lower than the current one the WT just kind of stops... any idea what i'm trying to say?

okay - i guess i'll have to read your post a few more times to understand what's going on :) but i can probably find time to remove the crystals from SIDs and wire them to the core. i'll report ASAP.

hmm i'll need 6 cores (4xSID + FM + SEQ)

great! what about the current draw from the cores/LCDs? will the C64 fuse hold?

i'm planning to stuff MBSID, MBSEQ and MBFM into a single suitcase. MBSID already works, but i'm wondering if it's possible to at least supply power for the MBSEQ from the same (C64) psu? what about MBFM? i understand i need a 2x12V supply for the OPL3 module but what about the core? it would be FANTASTIC if i could do it all with just 1 PSU but if not possible then at least as few as possible... please recommendations.

that totally depends on: 1. the tools you already have (soldering iron, PCB holders, all the accesories) - i had none and i've thrown like 150 euro just for that. you can do it much cheaper but i really recommend good soldering iron. 2. the buttons and knobs you chose - the prices can vary a big deal. others will tell you their prices cause i still haven't bought mine but judging from the samples i got from SIFAM i think i'll go with their knobs - they will cost me around 10UKP. 3. the front panel and the case - this can be the biggest expense, especially the frontpanel. you can order it from shaeffer but then it will cost you more than 100 euro. or you can do it yourself and learn a LOT of new things in the process :) when i finish mine (though i won't be really finished cause i've a plan to stuff an MBSEQ and MBFM in the same box) my total expenses will probably be over 300 euro but mostly due to the tools. but i know i'll need them in the future - i'm already looking at the PAIA 9700 modular... ;) building DIY synths is fantastic fun and it's totally changed my life. i know i will keep doing it till i die. my dream is a full-sized modular and i know i'll have it finished one day :) and MIDIBOX introduced me to this :D

hehe my goal is to build a MBSID, MBSEQ and MBFM into a suitcase. i've already got it planned and the MBSID is nearly finished. next is MBSEQ and then MBFM. that one will be the toughest (because of the PSU...)

here are a few patches for you Thorsten (and others): http://s12.yousendit.com/d.aspx?id=3P1VW5DIU6V480UTCJEBGD4TTR i hope anyone likes any of them and can use them :/ they sound much better on 8580 but also pretty much recognizable on 6581. one thing i noticed - the osc envelope gets retriggered randomly when using WT. is that a known error? it happens on both chips. anyway - all the samples are 1OSC, max 1 ENV, max 1 LFO. no filters. i think the bassdrums and the snares are the best but the cymbals are also usable. oops i just remembered i forgot the clap :D i'll see what i can do. any feedback appreciated.

i'm really sorry TK - this weekend was totally crazy for me - i had to help moving my father and assembling his kitchen :/ i'll really try hard to find time during this week. the following goes for 6581. haven't tried it with 8580 yet. from what i was trying i can say this - the bassdrums can sound pretty good, especially for 808-like sounds. triangular waveform has very quiet higher harmonics and sounds almost like sine even without the lowpass filter. other waveforms result in distorted/overdriven-like sound, can be used for gabber. combined waveforms aren't useful for bassdrums cause they're really low on bass. the high hats will be no problem. the pitched noise offers a variety of tonal options. even without filters. toms will be fine, similar to bassdrum. snares will be the toughest... how fast can the LFO go? how fast can the WT go? it's really nice to have the "tone" in the snare sound, otherwise it's way too hollow. something could be done with the lower frequency noise... i'll see. other percussion sounds could probably realized without big problems and i don't think they're as critical as the basic ones. i'm wondering - would it be possible to set the filter on/off per-patch? since the patches are only 1 channel it could be done. or do you think the popping when turning the filter channels on/off would be too annoying? it would be really useful. others could post their experience and observations on drum sounds design here. what do you guys think about the snares?

building it is the real fun. i've never soldered anything before this mbsid in my life. and now i've only got to finish my frontplate and it's done. for all the questions about where to get SIDs, PCBs, ... - use the forum's search function. it's been discussed/explained a few times alredy.

oh so you moved my post ;D i thought i posted in the wrong thread haha. no problem man.

from thorsten's post i'd say it's possible for cutoff but not for resonance.

hehe yeah capacitors not resistors ;)

yes it's that one. the internal communication between the master core and the slave cores is still via midi (sysex) but you don't need to bother with that.

they always go between the VDD pin of the IC and ground plane on the board, as close as possible to the chip (pins). on the SID: on the CORE: if you're not sure what pins are VSS and GND check out the PDF schematics: SID: http://www.ucapps.de/mbhp/mbhp_sid.pdf CORE: http://www.ucapps.de/mbhp/mbhp_core.pdf (they're even in those pdf schematics) for help - the "ground plane" is like one big wire that has ground voltage and since it's used very much in the circuits it's usually pretty much everywhere - it's the big copper trace usually around the entire circuit. and the IC's VSS pin is connected there too.

yeah just 1 midi in and 1 out. that's the whole point of the 1master+3slaves idea. you can assign each to it's own midi channel if you want.

the first mp3 is mono ???