TK.

Ich werde am Wochenende eine Reichelt Bestellung aufsetzen, die Diode kann ich dann gleich mitbestellen - Deine Adresse habe ich ja noch ;) Gruss, Thorsten.

It seems that the wrong code is selected by default which was inserted by Jim for scanning a Panasonic keyboard. Could you please try the application with the #if switch in SM_NotifyToggle set to 1? No problem, just swap again. As stated in this schematic: http://www.ucapps.de/mbhp/mbhp_scan_matrix1.pdf rows/columns have to be swapped if the cathodes of your hardware are connected together. In the software, SM_SWAP_CR has to be set to 1 (so, a second change is required in sm_fast.inc) Are the cathodes or anodes connected together on your keyboard? Best Regards, Thorsten. P.S.: I uploaded an updated version where the right decoding is selected: sm_example2_v1d.zip under http://www.ucapps.de/mios_download.html Press the refresh button of your webbrowser if you see the previous version.

Shipped today: schokobaer mortimer Spoth74 Breeze Best Regards, Thorsten.

Ok, seems that I can't help you - I'm out. Best Regards, Thorsten.

Hi Jilt, welcome back! I remember that our last conversation was in 2001! :) There is a big problem with the "internal DAC" channels of STM32: the output is located at the same pins which are used for SD Card accesses, and there is no alternative pin mapping. Therefore unfortunately these channels cannot be supported by the MBSEQ V4 application. If this restriction wouldn't exist, you could amplify the outputs with the same OP Amp circuit as used by the MBHP_AOUT_LC module: http://www.ucapps.de/mbhp_aout_lc.html So, you will need one of the MBHP_AOUT* modules. AOUT_NG is the most preferable solution, AOUT_LC the cheapest, and the original AOUT if you don't like SMD soldering (but it's more expensive) Gate/Trigger pins at J5 can be shifted to 5V with a 74HC541 buffer IC, see this datasheet: http://www.standardics.nxp.com/products/hc/datasheet/74hc541.74hct541.pdf Pin 1 and 19: OE# connected to ground Pin 10: to ground as well Pin 20: to 5V Pin 2..9 are the inputs Pin 11..18 are the outputs Best Regards, Thorsten.

Phil, we need a mutex for posting replies ;) Best Regards, Thorsten.

Not required, you can order the 3 x DINX4 and 1 x DOUTX4 module directly from SmashTV - they are better quality anyhow. In this case you would have to order 4 x MBHP_IIC_MIDI modules yes Where are you located? You could also oder the LCDs from a mailorder company, together with buttons/LEDs and other stuff I would order the momentary push buttons from a mailorder company to save money Can only be perfectly answered if we know where you are living Alternatively you could order them from Voti, the order number is given here: http://www.ucapps.de/midibox_seq_manual_hw.html yes Where did you found a reference to BankSticks for V4? They have been replaced by a SD Card, see also complete part list of the V4 project: http://www.ucapps.de/midibox_seq_manual_hw.html Available in each supermarket, see also "Ultra Low Cost Adapter" here: http://www.ucapps.de/mbhp_sdcard.html Best Regards, Thorsten.

Here are some DIY instructions: http://www.instructables.com/id/The-Most-Useless-Machine/

Great! :) Best Regards, Thorsten.

Several features of the MBHP_CORE_STM32 module are missing, like 5V->3.3V voltage converters, USB socket, MIDI sockets, LCD voltage converter, etc. Why do you think that this is a good replacement? What are you planning to do exactly with the STM32? Best Regards, Thorsten.

Hi Kris, thats strange! RC should toggle for ca. 1 uS each millisecond SI should toggle depending on the button states if RC captures the button inputs. No, there shouldn't be a compatibility problem. You can verify this by uploading the MIDIO128 application. More troubleshooting tips related to the DIN module can be found here (search for "Testing"): http://www.midibox.org/dokuwiki/doku.php?id=home:mbhp:module:din Best Regards, Thorsten.

Yes, please! :) Than more than better Best Regards, Thorsten.

I've a deja vu... we had this discussion some time ago: Wilba wrote the conclusion at the end of this article - it's still valid. So, if you only want to save shipping costs (because you won't get the PCBs/kits cheaper if you run a bulk order, SmashTV already offers best prices), then search for people to join the order in *your country* to share the international shipping costs (US $30), and to reduce local shipping costs. Best Regards, Thorsten.

You can edit this on the Sammich as well. :) This is an old tutorial that I wrote for V1, it's only a subset of V2 but KEY1/2/3/4 was already available: http://www.ucapps.de/howto_sid_wavetables_3.html Instead of using "Goto" you have to set the loop parameter, and the CC assignments are different (Par#252/253/254/255 instead of CC#9/10/11) Best Regards, Thorsten.

Alright - this is what you can do with the WT sequencer :) See the WT patterns of "A064 ARPSEQ One" upwards Best Regards, Thorsten.

Could you give an example, how this is realized on the Virus? E.g. a .mid file, or just a snapshot of a pianoroll editor, so that we can see when notes are played. Btw.: alternatively you could use one of the 4 WT sequencers to create your own arpeggio texture. Did you already consider this? Best Regards, Thorsten.

See my SwinSID review. Swinkels has released the source code, so that it can be ported to other derivatives. A fully stuffed MBSID V2 (with 4 PIC cores) can control 4 Atmega based SwinSIDs = 8 emulated SIDs = 24 SID voices. I'm already working on MBSID V3 which uses a STM32 derivative instead of PIC. With this microcontroller the number of SIDs isn't really limited anymore, it's only a question of memory consumption and update frequency. A STM32 can even emulate SIDs in parallel (see nILS' recent postings), so that no Atmega based "companion chip" is required. Best Regards, Thorsten.

Alright, please try RC35: o modulation source "KEY" now uses current frequency instead of key number to consider frequency sweeps correctly o bugfix for "jump to page" (empty page if current item position outside new page) o bugfix for knob page (min/max value modified Pa1 if multiple SIDs selected) [/code] Best Regards, Thorsten.

Then the problem seems to be located somewhere else. There is a trick which forces a reboot without power-cycling the core: tap a cable from ground to pin #1 of the PIC for a short moment - this will reset the core. It would be interesting, if this helps. Yes, for safety reasons I removed this hint, because the danger is too high that the upload fails if somebody tries this under "unstable" conditions (e.g. firmware overloaded, so that MIDI stream gets corrupted) Unlikely that this happened, but if you don't want to find out the exact reason for the failure, burning the bootloader makes sense... There is no reason why it doesn't make sense to upload v1.9g Best Regards, Thorsten.

Thanks - it's very likely that I can release an update today, but before I need some more help from your side: Ok, now I get it - (only) when multiple SID engines are selected, the Min parameter is copied to the Pa1 parameter as well. Yes, the Env/Misc/Assign selection behaves strange - thats probably related to the latest changes in RC34 (see ChangeLog) - improvable. Does this only happen in conjunction with this button function? Best Regards, Thorsten.

No, such MIDI events are not transmitted via CAN, and it would be too difficult to add this compared to a proper ensemble configuration done by the user - I will add this to the documentation. Has anybody else noticed the same? As always: I need step-by-step instructions. Best Regards, Thorsten.

To get some additional infomations: does MIOS Studio receive the initial upload request during startup with the master core? Best Regards, Thorsten.

Ob ein Geraet durch eine Masseschleife kaputt gehen kann oder nicht, haengt u.A. vom Netzteil ab. Die einfachste und sicherste Loesung waere in Deinem Fall, die Masseverbindung am MIDI Out des Core Modules zu trennen, und zwar direkt an der Leiterplatte (bzw. an der MIDI Buchse). So laeufst Du nicht Gefahr, dass das Core Modul abermals eine Ueberspannung abbekommt, wenn Du mal ein anderes (unmodifiziertes) MIDI Kabel anschliessen solltest. Alternativ koenntest Du ein besseres Netzteil verwenden - wie wird das Core Modul momentan versorgt? Gruss, Thorsten.

No, it isn't required to upload the sequencer application again (so long you are using MIOS V1.9g and the latest MBSEQ V3 release v3.4f) The DOUT registers won't be damaged if you connected them to J9 instead of J8 by fault. It's more likely an additional wiring or soldering error. Check especially the CORE:J8:DO->DOUT:J1:DO, CORE:J8:SC->DOUT:J1:SC and CORE:J8:RC->DOUT:J1:RC connections If you don't find the error visually, but own a multimeter, the srio_interconnection test helps you to measure the voltage levels: Best Regards, Thorsten.

So, you compiled MIOS by yourself and uploaded it to your core before uploading the application? If this modification hasn't caused an effect, then I assume an handling error (please describe more exactly what you did to clarify the issue). Since I assume an handling error, I attached a precompiled .hex file so that you can easily compare the results. Before continuing with speculations, could you please give me some feedback if the .hex file I gave you is working at your side. There are no other changes which are required, it's really straightforward. Best Regards, Thorsten.