TK.

Hi Michael, divisions are always time consuming, and with floating point values it will take even longer to get the result. For scaling values I'm normaly using a 8*8 bit multiplication, the scaled result will be in the high byte of the result register. Here a function which you can use (it's from the sid_random application, and it's assembler optimized) unsigned char Scale_8bit(unsigned char value, unsigned char min, unsigned char max) { // scaled value is (<8-bit random> * <range>) >> 8 PRODL = value; // 8bit value PRODH = max-min+1; // range __asm movf _PRODL, W mulwf _PRODH, 0 __endasm; return min + PRODH; } [/code] Best Regards, Thorsten.

Maybe you will like also this stuff: http://www.binaryzone.org/joytoy.php Best Regards, Thorsten.

Could it be that there is a feedback loop caused by MIDI-Ox or MIOS Studio? In MIOS Studio, ensure that there is no direct connection between MIDI In and MIDI Out of your core. Check the same in the port routing window of MIDI-Ox (for the case that you are using this software). Please also remember: so long no module is connected to the core, and the MB64 application is running, it's required to tie all analog inputs of J5 to ground in order to avoid random MIDI events. Only tie the analog inputs, not the J5:Vd (+5V) pin to ground! -> http://www.ucapps.de/mbhp/mbhp_core.pdf Best Regards, Thorsten.

you're welcome! :) The firmware is final now, next step is to write the documentation for so many new options (ooof!) yes, but the AOUT module is controlled by MIDIbox SID specific parameters, and there is no special menu which allows you to customize the function of each CV output. It can only be changed directly in the software. Currently the AOUT_LC outputs the filter and resonance parameter. Both can be modulated with LFOs and EGs, see also this demo: http://www.midibox.org/forum/index.php?topic=5633.0 Best Regards, Thorsten.

You could create a table which maps the values... Best Regards, Thorsten.

I'm just waiting until Google will provide the possibility to create and send the annual tax declaration, then they really know everything of the individuals ;-) Best Regards, Thorsten.

Hi Flo, you need a special variant of MIDIbox CV in order to get the module running (it's currently only supported by a beta version of MIDIbox SID). The gate will be available at the J5 port of the core module, which is normaly used for analog inputs... I'm still working on the next MBCV release, e.g. a friend brought me his MS20 synth, so that I'm able to implement and especially to test the V/Hz output curve feature. Also a 96ppqn sync output is under construction. If nothing unexpected happens, I will release it this weekend. Best Regards, Thorsten.

The PIC18F4520 won't work, I've already tested it: it has the same EUSART bug. Btw.: three weeks ago I felt so bored, that I contacted the microchip support again in order to inform them, that the PIC18F4620 as well as the PIC18F4520 has the same bug. As expected they were not informed about this issue. Two days later they updated the 18F4520 errata sheet and asked me if the bug is in the sheet now (seems to be a more comfortable way than reading my previous messages) --- it wasn't ;-) This discussion is still continuing, in the meantime I sent them two programs which allow to reproduce the bug within one second... Best Regards, Thorsten.

Very unlikely (however, I don't know how much you've tortured the PIC ;-) Do you see an upload request during power-on? Best Regards, Thorsten.

Brian stopped with his developments long time ago, and since some months there is no sign of life from Hiroo anymore. I wrote him a mail, but never got an answer :-/ Best Regards, Thorsten.

Hi, yes, both is possible without problems. In order to send a sequence of bytes, you need to use "meta events", a description with some examples can be found in mb64_meta.inc All pots provide "min" and "max" values, you can use them to reduce the value range - see midibox64.ini, which is part of the "mk_syx" package. Best Regards, Thorsten.

Hi Rene, if you start the "convert.bat" batch file, all these .syx with the appr. device IDs will be created automatically (read the .bat file in order to see, which commands are used). In principle you've done everything correctly. I'm sure that you will be able to find out, why the upload to Slave1 didn't work (based on your descriptions it's hard to find this out). General hint: the upload with MIOS Studio is more secore, since it notifies you if a block hasn't been uploaded correctly. Now you are at the same point like Wisefire, so just read this thread: http://www.midibox.org/forum/index.php?topic=5277.msg35621#msg35621 Best Regards, Thorsten.

Hi, this remembers me, that somebody had a very similar problem. After a lot of mail exchanges, it turned out, that he used a bad parallel cable to the PC. Are you using a new one? And how long is it? Another thing what could be interesting: what is the Vpp voltage during programming? Is it stable? Best Regards, Thorsten.

Hi Adam, MIOS has to be uploaded within 2 seconds after power-on. Did you take this into account? Best Regards, Thorsten.

Hallo Claudio, meiner Meinung nach ist der Background Noise ist nicht so laut, dass es sich lohnen wuerde, soviel Aufwand reinzustecken. Karl Dalen hat schomal einen aehnlichen Vorschlag gemacht (siehe http://www.midibox.org/forum/index.php?topic=4075.0), aber ich persoenlich habe kein Interesse, diesen auch umzusetzen. Vielleicht jemand anderes? Gruss, Thorsten.

Hi Rene, since some weeks I'm thinking about a new "HowTo" page for the SID setup procedure, but the problem is, that I haven't found the "newbie-friendliest" solution yet. For somebody who has worked with (some!) MIOS projects before, it's easy to understand what has to be taken into account in this special MIDI wiring which is used by MIDIbox SID (e.g., since the MIDI Outs of the slaves are not connected to the PC, the "don't use feedback from core" switch in MIOS Studio has to be enabled. Another point: the slave needs a reset pulse for uploading MIOS via 1st level bootloader, this can be done by tipping ground to pin 1 of the slave SID). At the end I think the newbie-friendliest method to setup the slaves which doesn't require much explanations is: don't follow the comfortable, but the easiest way! Unplug the PIC from the master module, plug the PIC which is used as slave into this IC socket, and program MIOS and the application from there. Thereafter the PIC is ready for use and you can plug it into the slave core socket again. Since you've programmed the master core successfully, doing the same for the slave shouldn't be that difficult anymore (check the device ID!). It doesn't require any knowledge about how to enable the MIDI merger without a Link button (beside of the SysEx string, you could also send a MIOS_MIDI_MergerSet function call via MIOS Studio), it is less error prone (because who knows if the slave module works, and that master and core are linked correctly?), and you have the LCD in order to check if the application is running. Please let me know how long it took to setup the slaves based on this method. If it works without problems, I will change the documentation at the csB page. JSynthLib: take care, the official JSynthLib release has a bug in the MIDIbox SID editor (which wasn't my fault...), a modified version can be found here: http://www.midibox.org/jsynthlib/JSynthLib-0.20.0_midibox_mod1.jar.zip Best Regards, Thorsten.

Hi Kokoon, you could ask the guy to assemble the source code for the PIC18F452, it's nearly source-code compatible. He only needs to change the baudrate settings. You could also use the bootstrap loader to upload the code like you would do it with MIOS. It's only important that the program starts with two "goto"'s to the start label (the first one will be overwritten by the BSL) Best Regards, Thorsten.

Hallo Andreas, stimmt - ich habe verschwiegen, dass ich zusaetzlich zum 2x12V Netzteil noch ein davon voellig getrenntes 5V Netzteil gebaut habe. Dies hat den Vorteil, dass man sich um die Spannungsfilterung keine Gedanken machen muss (digitale Stoerspannungen streuen nicht auf die analoge Schaltung ein). Ausserdem wird der 7805 nicht so heiss, wenn man ihn mit weniger Spannung (ca. 7VDC) betreibt. 12V vor dem 7805 waere bei diesem hohen Stromverbrauch zu viel. Ein Foto gibt es hier http://www.midibox.org/midibox_fm_photos/3.html Dass auf der Lochrasterplatine ein Gleichrichter/Elko/7805 fuer den 5V Zweig vorgesehen ist, hat historische Gruende - die Stabilisierungsschaltung auf der Core Platine ist voellig ausreichend. Ja, MBFM und MBSEQ haben einen Merger eingebaut. Bei der MBFM heisst er "MIDIbox Link" (siehe Doku), beim MBSEQ kann man ihn im MIDI Menue einschalten. Gruss, Thorsten.

Here a new tutorial which describes, how to modulate sound parameters with the wavetable sequencer: http://www.ucapps.de/howto_sid_wavetables_2.html Have fun! :) Best Regards, Thorsten.

Hallo Andreas, Die Schaltung von meinem MBFM Netzteil findest Du hier: http://www.ucapps.de/mbhp/mbhp_opl3_psu.pdf Ja, das ist moeglich. Es gibt verschiedene Routingmoeglichkeiten fuer die verschiedenen Einsatzwecke. Fuer Noten eignet sich AOUT1-4 am besten. In diesem Fall wird der Notenwert an CV Kanal 1/3/5 oder 7 weitergeleitet, und der Velocitywert an CV Kanal 2/4/6 oder 8 Das Ziel "AOUT" laesst sich im Event Menu anwaehlen, und zwar fuer jeden Track separat. Statt eines MIDI Events sendet der Sequenzer den Step also einfach an das CV Modul. Ja Ja - wie ich sehe, hast Du doch alles richtig verstanden :) 2x40 LCDs gibt es guenstiger bei voti.nl (kann man gleich zusammen mit den Encodern bestellen). Gehaeuse und Frontplatte: hier sind die anderen gefragt Gruss, Thorsten.

Ok, sample is angekommen. Der Sound hoert sich bereits ziemlich clean an, kein Brummen und kein Zirben, welches man durch zusaetzliche Hardware unterdruecken koennte. Was im Hintergrund noch uebrig bleibt, ist der Output der drei Oszillatoren. In Deinem Beispiel wird nur ein Oszillator verwendet, die anderen beiden stehen auf "Off". Das kann auch so bleiben, ich wuerde Dir jedoch empfehlen, diese Oszillatoren genauso wie den ersten einzustellen. Zusaetzlich koenntest Du sie noch auf -64 transponieren, dadurch sollten sie wesentlich leiser werden. Mehr laesst sich nicht machen - der VCA kann einfach die OSC Outputs nicht komplett runterregeln. Gruss, Thorsten.

yes, all unused analog inputs of the J5 connector have to be connected to ground as well, no other pins of the PIC (!) Best Regards, Thorsten.

Hi Justin, some applications require this (not sure if this is the case for MB64), so just add a "movf MIOS_PARAMETER1, W" before branching to the handler. it looks very compact :) Best Regards, Thorsten.

I like the band, too! I've purchased the Live DVD from http://www.c64audio.com/ some time ago, their performance is just great! :) Best Regards, Thorsten.

Hi Verbel, pay attention for the faders, there are different ones! For audio applications, they normaly have a logarithmic output curve, but such a characteristic is absolutely unusable for MIDI. Especially stereo faders are only for audio, so it should be a mono fader with 10k linear output (it's not possible to convert log->linear properly!). For the buttons look for "normaly open" types, it doesn't matter, how many poles they have, but single pole buttons are normaly cheaper. Required Modules: MBHP_CORE, MBHP_AINX4 (for faders/pots) and MBHP_DINX4 (for buttons). MBHP_USB isn't really cheaper than a commercial MIDI interface today, and this project is especially not easy to handle for newbies, therefore just buy an interface for less than 40 EUR Or take the MBHP_LTC module for the to-COM option MBHP_BURNER: not required if you buy the PIC at SmashTV's or Mike's Shop, they will program the bootstrap loader into the flash. But you need to tell them, if the to-COM baudrate should be enabled or not, because this option cannot be easily changed via MIDI Best Regards, Thorsten.