TK.

Well done, Smash! :-) Now the users are able to publish and maintain their own content, this is a big step into the direction of a "self-governing" community. I noticed the same problem like PayC, the link to the new portal site via http://www.midibox.org doesn't work, it leads to the old portal instead. Best Regards, Thorsten.

Hi Dan, do you see two Audio devices in MIDI-Ox or only one? How did you connect your core module to the MBHP_USB? via MIDIbox Link or via optocouplers? Best Regards, Thorsten.

Your Chip is working and it's normal that the vendor request hangs up when the vend_ax.hex firmware is not loaded. Once the MBHP_USB firmware is running, the control panel will report, that no Cypress device is detected... so it seems that the firmware is not loaded from EEPROM during power-on. I guess that there is a problem between the EEPROM and the cypress chip, could you please measure the voltages at pin 1 & 8 (-> 3.3V against Vss) and 2, 3, 4, 7 (-> -3.3V against Vdd) first? The voltages at Pin 5 & 6 should also be 3.3V against Vss (the EEPROM will only be accessed during the first miliseconds after reset) See also: http://www.ucapps.de/mbhp/mbhp_usb.pdf Best Regards, Thorsten.

Es koennte sein, dass der Trackball keine sauberen digitale Signale liefert. Du muesstest also nochmal einen Schmitt Trigger zwischenschalten, bspw. 4093 Siehe auch: http://www.doctronics.co.uk/chuckles.htm Gruss, Thorsten.

I've now uploaded a new package version of MBHP_USB which contains a .syx file with the V1.1 firmware Just follow the instructions which are given in the README.txt http://www.ucapps.de/mbhp/mbhp_usb_v1_1b.zip Best Regards, Thorsten.

I don't know the ELV programmer, if it can ready .hex, then use the .hex file, if it allows to upload a binary, then use the .iic file However, I've now uploaded a new package version of MBHP_USB which contains a .syx file with the V1.1 firmware Just follow the instructions which are given in the README.txt http://www.ucapps.de/mbhp/mbhp_usb_v1_1b.zip Best Regards, Thorsten.

Hi Doc, very interesting. Yes, you can burn the EEPROM with any programmer, it could also be programmed via a MIOS core like a BankStick (which would solve D2k's problem), but for this I've to prepare a special .syx file Best Regards, Thorsten.

P.S.: if there are vendors which also provide a USB interfaced based on the standardized USB MIDI protocol, you will maybe found a troubleshooting guide (or an alternative driver) on their site. I haven't found the time to search for such solutions yet (since I don't have access to a Win2k computer, I cannot test it) Best Regards, Thorsten.

"USB midi" or "USB audio device" Best Regards, Thorsten.

Mit dem SysEx Loader von Serge kann man keinen Code aufspielen. Das geht momentan nur mit MIDI-Ox und auch nur mit den Delay-Settings, die auf der Bootstrap-Loader Seite angegeben sind. Wilba bereitet gerade ein neues Java-Tool vor, das den Upload vereinfacht, aber bis dahin bitte genaustens an die Anweisungen halten. http://www.ucapps.de/mios_bootstrap.html Es gibt auch eine MIDI Troubleshooting Guide, die Du erstmal durcharbeiten koenntest - vielleicht ist das MIDI Interface noch nicht richtig angeschlossen? http://www.ucapps.de/howto_debug_midi.html Das Display sollte korrekt initialisiert werden, sobald MIOS aufgeladen wurde Gruss, Thorsten.

Thanks, I will check this on the next time slot References for the search function: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1074984354;start=0#1 http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1074547353 Best Regards, Thorsten.

Hi Dan, maybe it doesn't install because you've tried too much before? Somewhere under "System Control -> Device Manager" it is possible to remove the driver which is assigned to the connected USB device. After doing this, disconnect/connect the module (you can also use the powerline jumper near by the USB socket) and WinXP should ask for the new driver again. Best Regards, Thorsten.

Hi Doc, it could be a problem with Win2k, because two other users reported the same problem, they are not able to get the MBHP_USB running under this OS. One of them tried the same module under WinME, and there it works fine. It also works under WinXP and Linux - so it must be a M$ issue. Maybe the Microsoft Knowledge base gives you some input? Best Regards, Thorsten.

Don't panic, I will check this sooner or later... maybe a bug, maybe a misconfiguration... you don't need to distribute your postings over different boards ;-) Are you able to change the bank with a "program change" command at MIDI channel 16? Best Regards, Thorsten.

Hi, no, it's just a software enhancement. No additional core module is required. In difference to the original AOUT schematic the module has to be connected to pin RC.0, RC.1 and RC.3 (J6 of the core module) Best Regards, Thorsten. /edit: pins corrected

Die Frage ist viel eher, was Du auf solch einem grossen Display noch zusaetzlich anzeigen moechtest, was man nicht auch auf 2 2x40 Displays anzeigen koennte. Das Bildschirmlayout muesstest Du selbst programmieren, dabei koennen Dir nur Leute helfen, die das gleiche Display besitzen. Und wenn die Routinen nicht geschickt genug implementiert sind, kann es durchaus zu einem hoerbaren Jitter kommen (siehe den MIDIbox SID Issue weiter unten). Von der Hardwareseite spricht nichts dagegen, 4x40 LCDs sind in der Regel mit zwei HD44780 kompatiblen Chips bestueckt, und lassen sich genauso wie 2 getrennte CLCDs anschliessen. Gruss, Thorsten.

yes, it's well hidden :-/ -> Design Resources -> Select "Developer Boards", "Universal Serial Bus", "USB Full Speed Peripherals" -> Go -> select "Developer Kit: AN2131-DK001 EZ-USB Development Kit" -> Download "EZ-USB Development Tools V2.61.700" and install it -> Unplug the EEPROM and reboot your PC thereafter the cypress chip should be regognized and the Control Panel should work. If you've more Windows experiences like me, could you please try another way: could you try to extract and install the driver from the package w/o starting the setup program? If this works, we could provide a smaller .zip file for other MBHP_USB users which only contains the driver itself Best Regards, Thorsten.

Hi Chris, you can control the effects from the MIDIbox, means: just use 10k pots and connect them to the analog inputs, and use an AOUT as CV out. The MB64 application just forwards the CV Input to the CV Out, and it allows you to send and receive MIDI and to store/restore settings (unfortunately only 16 setups with each BankStick, since it's optimized for 128 MIDI entries per bank, but you could also change the software for storing 128 setups and more if less number of entries are required) I just noticed that this phaser has no CV inputs, but requires "digital pots", which are similar to a DAC (and identical from the software point of view), but which provide a variable resistance instead of a variable voltage. You will find some infos concerning digital pots in older articles (use the search function of this forum) Btw.: I guess for such Fx gear 7bit resolution is more than enough! Best Regards, Thorsten.

You could send me a backup copy of the flash and the BankStick via email, so that I can try your actual configuration on my own Box. Follow these instructions: http://www.ucapps.de/mios/mios_backup.txt Best Regards, Thorsten.

Hi Dan, I'm not sure about the firmware version, v1.0 worked fine under Windows ME, but didn't work under Linux. So I rearranged the descriptors in v1.1. But the descriptors cannot be the reason for the feedback. > Why would the 2 midi i/o behave okay tho? Totaly unsure, because the first has a bad soldering joint? In the meantime I'm also using WinXP, the installation of the Cypress USB driver was successfull (but I used the original package from http://www.cypress.com --- unfortunately 65 MB!), the MIDI ports are running w/o problems. Best Regards, Thorsten.

Not sure about the price, Maxim sells it for $11.95 (@1k!) Maybe http://www.findchips.com helps I just order two free samples from http://www.maxim-ic.com Best Regards, Thorsten.

Yes, you can. The LCD driver takes care for conflicts via software (otherwise my MIDIbox LC wouldn't run with a single core module...) Best Regards, Thorsten.

Hi Chris, this is one of the easiest jobs what a MIOS core can do... ;-) The current MIDIbox 64 already provides 64 CV inputs and 8 CV Outs. 64 CV Outs are planned (I'm waiting for some ordered sample&hold chips to test this possibility). Maximum Resolution of the CV Ins: 10 bit Maximum Resolution of the CV Outs: 12 bit NRPN is not provided by the MB64 application by default, but could be implemented in a special application dedicated for CV Best Regards, Thorsten.

Hi Wilba, a more general answer: since one month I'm working from time to time on a new SID release, some of the new features are suggested by Jess D. Skov-Nielsen (an experienced sound designer with a lot of SID knowledge). Here a list of functions which are already implemented and tested: optional oscillator phase synchronization for more percussive sounds non-linear envelopes with flexible CURVE parameter which allows you to bend the attack, decay and/or release curve to upward/downward direction optimized linear response of the 8580 filter correctly calculated Note->frequency table more stable wavetable sequencer timings (based on experiences with MIDIbox SEQ) optimized display handler to avoid long delays of more than 1 mS minimal AOUT support (7 CV out assigned to the existing outputs of the modulation matrix, 1 channel to the filter resonance parameter What I plan to implement after MIDIbox SEQ has been released: 7 dedicated modulation matrix outputs especially for the CV outs note/pitchbend assigned to the 8th CV out 1 Note gate and 1 sequencer clock out a special button combination which switches the LED matrix of the control surface between common and AOUT matrix --- I will never change my own panel anymore, therefore this solution a second MIDI channel to control the AOUTs via MIDI The last point requires some conceptional changes (internally), therefore this effort can only be made by myself (I know how, but I guess that the implementation and testing will take at least 2 days) - on the other hand: the current solution already works very fine. You can connect an analog filter to the SID and control it with the filter out of the modulation matrix (the SID filter should switched off), or you can use the three PW outs of the matrix when only saw/tri/noise sounds are played, and/or additionally the pitch outs when oscillators are disabled. But this solution won't be compatible with the planned one, therefore I haven't released it yet. Btw.: the AOUT module gives me the possibility to display the envelopes - it was a very useful debugging feature :) Here some impressions: Best Regards, Thorsten.

me too - both are working fine Best Regards, Thorsten