TK.

Hi, you could implement such a SHIFT button on a similar way like "SEQ_BUTTON_All" (just toggle a flag stored in a memory location). Thereafter you have to change SEQ_BUTTON_GP, so that an offset of 8 is added to button 0-7 when the SHIFT function is activated, and you have to modify SEQ_LED_UpdateIRQ, so that either IRQ_TMP1 or IRQ_TMP2 is transfered to the "DEFAULT_GP_DOUT_SR0 - 1" shift register. Best Regards, Thorsten.

there are already easy to use parameters to generate detuned notes, e.g. the "Detune" parameter, which automatically detunes all 6 oscillators of a SID core (differently for left/right side), or the 6 finetune parameters which allow to detune the oscillators individually. Each SID core has it's own set of detune/finetune parameters - so, your requested feature is already available, you only have to use it... ;) But you are right, that an alternative note tuning table would be nice Do you have an algorithm or a ready made frequency table for phytagorian tuning? It isn't possible to store alternative tuning tables in BankStick, as it has to be accessed frequently by the sound engine from an ISR. But it would be possible to store it in flash memory as long as there is some memory free (and if there should be too many new features in future, the alternative tables have to be removed partly, or limited to a certain frequency range). The table could only be edited directly in the assembler file - I don't think that it is worth the effort to integrate an editor into the CS, but somebody could develop a GUI which generates the assembler file. Best Regards, Thorsten.

of course thats correct - in addition, the ENC_NotifyChange() has to be enhanced, so that MIDI events are sent on encoder movements. E.g.: void ENC_NotifyChange(unsigned char encoder, char incrementer) __wparam { MIOS_MIDI_TxBufferPut(0xb0); // CC at MIDI Channel #1 MIOS_MIDI_TxBufferPut(0x10 + encoder); // CC# is 0x10 (16) for first encoder MIOS_MIDI_TxBufferPut((0x40 + incrementer) & 0x7f); // this "40 +/- speed" format is used by NI software and some others } [/code] to send relative CC events (will work fine with Traktor) Best Regards, Thorsten.

Hallo Lui, fuer Dein erstes Posting funktioniert schon beachtlich viel - andere Newbies verzweifeln bereits am Bootloader! ;) Wenn die LEDs (wie im Video sehr schoen zu sehen) beim Einschalten aufflackern, ist die Polaritaet schonmal richtig. Ich nehme an, dass Du sie nach dem Schaltplan an den dritten und vierten 74HC595 angeschlossen hast - vermutlich liegt zwischen dem zweiten und dritten 74HC595 das Problem. Nimm nun den Schaltplan des MBHP_DOUT Moduls zur Hilfe: http://www.ucapps.de/mbhp/mbhp_doutx4.pdf - zwischen den SCLK und RCLK Pins muss eine direkte Verbindung bestehen, und IC2:O8 ist an IC3:SER angeschlossen - nimm einfach die ICs aus den Sockeln und "piepse" die Verbindungen durch. Vermutung: im Layout befindet sich zwischen IC2:O8 und IC3:SER eine Bruecke. Entweder fehlt sie, macht einen Kurzschluss (bspw. gegen Masse), oder sie ist nicht sauber angeloetet. Ein Fehler bei den SCLK und RCLK Pins ist eher unwahrscheinlich, weil die LEDs ansonsten permanent flackern wuerden. Ein kurzer Check schadet aber trotzdem nicht... Gruss, Thorsten.

Second envelope: the MBFM application already allocates almost the complete flash memory and RAM - also performance is very critical, so that such a change (which will require an additional modulation path) will quickly lead to MIDI buffer overruns. However, if you have hacker ambitions, you could remove existing features (e.g. second LFO or WT sequencer) to free memory, and add the second envelope if you want, but you have to consider that the complete infrastructure like Control Surface, SysEx Structure, Patch Manager, JSynthLib based Editor, etc. have to be adapted as well. Arpeggiator: same issue - but you can already use the WT sequencer for arpeggios (value 0x7c..0x7f assigned to Note CC will play Key1..4) - it's the same mechanism as used for MBSID V1 Best Regards, Thorsten.

Hallo Alex, danke fuer den Input! Habe doch glatt verpasst, dass es bei Pollin wieder guenstige LCDs gibt :) Da ich gerade zwei neue LCDs gebrauchen kann, werde ich auch gleich einen Panasonic Encoder mitbestellen und bei mir ausprobieren. Vielleicht kommt ein neuer Encoder Type dabei heraus... Gruss, Thorsten.

Falls Du eine fertige Applikation suchst: du koenntest einfach die MIDIO128 Applikation aufladen - hiermit lassen sich bereits bis zu 128 Relais ueber bis zu 4 MBHP_DOUTX4 Module ansteuern. Die MIDI Events sind frei konfigurierbar, per Default liegen die Ausgaenge auf MIDI Noten. Falls Du mal ein wenig Programmieren moechtest: das ist quasi ein Dreizeiler (wenn man die Kommentare rauslaesst ;-)) -> http://www.ucapps.de/mios_c_set_dout.html Falls 8 Pins ausreichen, koenntest Du statt eines DOUT Modules auch einfach die MBHP_CORE:J5 Pins direkt ansteuern. Auch hierfuer gibt es Programmierbeispiele. Gruss, Thorsten.

Probiere es mal mit der alten Version (v1.0.6), mit der neuen klappt die Benamung der MIDI Ports nicht mehr. Gruss, Thorsten.

Ploytec informed me, that the PCBs arrived today. I will get them together with the chips next week. PMs to people in the waiting list will be sent out once I find the time. Best Regards, Thorsten.

Bad news: according to the mmj website, the development of this library has been discontinued in July 2009 - support for 64bit Java cannot be expected, and even if 32bit JRE is selected under Snow Leopard, it won't work properly. Good news: it works perfectly with Mandolane (single user license available for ca. 6 EUR) Best Regards, Thorsten.

There is no need for using transistors, because digital pins will be in tristate (-> floating) once they are switched to input mode via the TRISx register. You are right! As a workaround you could connect a spare digital and an analog pin together. To measure the resistance, switch the digital pin into tristate mode. To drive the analog input, disable tristate mode and set the logic level (0/1) via LATx register This tutorial basically explains the same method I used for my STM32 based example. My example looks a bit more complicated, as it is prepared for multitasking. You want to allow multitasking for your application as well (I guess), e.g. to handle incoming MIDI data. If this isn't required, you could program it as a single thread in the Tick() hook, you could use MIOS_Delay() to insert delays between measurements, etc... Best Regards, Thorsten.

Ok, apparently the Device ID of your PIC is 70 instead of 00: F0 00 00 7E 40 70 01 F7 Solution: upload the change_id application (can be found in the MIOS download area) with device ID 70 selected in MIOS Studio. It will program a new ID, so that you can select Device ID 00 thereafter. You wrote: where did you set this? Something was wrong there... Best Regards, Thorsten.

Hi, there are several usecases for @ononly, e.g. triggering a CC or Note with the same number and a specific Velocity. Sometimes an event with value 0 is not wanted when the button is released, e.g. if you want to control a radio button element in Reaktor with multiple buttons. LEDs are not really supported for this mode, this would require a dedicated firmware which defines how the LEDs should be exactly controlled... Nothing will happen until the logic state of the switch changes... Did you already made some experiments with the firmware, or are these theoretical questions? Best Regards, Thorsten.

What is displayed in the MIDI IN Monitor window of MIOS Studio? And which operating system / MIDI Interface are you using? Best Regards, Thorsten.

Hi, sounds like a ground loop. "Starlike ground wiring" is very important here. Means: connect the ground/Vs pins of the core modules from a single point (e.g. from your PSU with separate wires), do the same for MF supply and fader ground pins. Don't chain them from one to another core module! Best Regards, Thorsten.

Thats a great case design! :) A patch/snapshot of a MB64 is not equal to the patch of a MBSID. While a MB64 patch stores pot and button positions, a MBSID patch contains sound informations in a special format. Storing a patch via SysEx request instead of the control surface is currently not supported - neither by MBSID V1, nor by V2. But it could be added with a simple hack - which MBSID version are you using exactly? Best Regards, Thorsten.

It even works without a buffer: http://www.ucapps.de/mbhp/mbhp_midi_gameport.gif Best Regards, Thorsten.

A new version is available (RC32) ChangeLog: o fixed strange Oct display output in Bassline Sequence Editor o added "DEFAULT_ENABLE_UPPER_WAVEFORMS" switch to setup_* files to enable the selection of additional waveforms for SwinSID o overworked Meter display mode in Bassline Mode (enjoy the effect! :) o changed behaviour of Play button: now it plays all SIDs regardless if they are selected or not. Dedicated SIDs can be played by pressing & holding the appr. SID buttons before pressing PLAY [/code] Best Regards, Thorsten.

I played a bit with mixed waveform based on the descriptions under http://www.dekadence64.org/sidwav.txt The results are not so promising: http://www.ucapps.de/tmp/mbsid_mixed_noise_1.mp3 demonstrates a single "F1 09 81" sequence. At the beginning you will hear a mixed waveform which quickly turns into noise. http://www.ucapps.de/tmp/mbsid_mixed_noise_2.mp3 "F1 09 81" are triggered with a definable delay (like the "Wavecomposer" is doing), which makes the mixed waveform more dominant. It's the effect which the name of the document calls "synthesized electric guitar" http://www.ucapps.de/tmp/mbsid_mixed_noise_3.mp3 I'm playing different notes to demonstrate, that the resulting sounds are not harmonic. So - yes, it's a new sound, but is it really useful? I used the WT with a hack for setting/clearing the testbit to check this. If it really would make sense to provide this as a feature, I would write a special function which resets the noise generator faster. On the other hand currently I don't see a real benefit. Best Regards, Thorsten.

It's part of MBSID V2 http://www.ucapps.de/midibox_sid_manual_b.html Best Regards, Thorsten.

The MP3 is now located here: http://www.ucapps.de/mp3/midibox_sid/mbsid_demo_random_patches.mp3 and the random patches are part of the MBSID V1 preset package. MBSID V2 provides an integrated random generator which allows to do the same without the need for .syx uploads (-> RND menu) Best Regards, Thorsten.

Update: I made a special arrangement with Ploytec which allows me to distribute GM5 devices very soon. 250 chips and 100 Mini PCBs are ordered, Nils will handle the bulk order for GM5x5x5 boards (please add your name if you are interested). Best Regards, Thorsten.

You are trying to upload the wrong file! The .hex file that you used allocates the bootloader range, the upload will be blocked so that the bootloader won't be overwritten. According to the README.txt, uploading pic18f452/midi/mios_v1_9f_pic18f452.hex is sufficient. Sidenote: it seems that it's time to remove the other .hex files, and only provide them on request to users who really *need* to update their old MIDIbox (with an installation which is older than two years) Best Regards, Thorsten.

Btw.: I'm going to arrange a special deal with Ploytec, so that it could be possible to get new GM5 chips soon, although we haven't reached the 250 pieces mark yet Best Regards, Thorsten.

Even hacking won't help here - Ploytec already pushed the chip to the limits ;) Best Regards, Thorsten.