TK.

The "click" happens since the DC offset changes at the audio output whenever different waveforms or filter modes are selected. With 6581, this effect is more dramatical than with 6582/8580. Unfortunately different volume values cause a DC offset change as well, otherwise MBSID could simply fade out/in the volume whenever a new patch is selected... Best Regards, Thorsten.

You can change the clock divider in the BPM menu. By default it's 4 for 24ppqn If you set it to 2, you get 48 ppqn With 1 you get 96 ppqn A start/stop signal is provided as well. The IO pin is specified in the setup_*.asm file Best Regards, Thorsten.

You have to replace the PIC18F452 by a PIC18F4620 (you could buy it with preburned bootloader from SmashTV), and you have to add a 1k pull-up resistor to J4:RC Best Regards, Thorsten.

Although it isn't standard, most software supports various "relative CC" event formats, and it's easy to implement this in C. However, this seems to be a double-post, Ultra asked for the same: http://www.midibox.org/forum/index.php/topic,11254.msg88492.html#msg88492 Best Regards, Thorsten.

Did you already try this example? -> http://www.ucapps.de/mios_c_send_enc_rel.html It sends relative events (0x40 +/- <speed>) - if you need a different format, just change the ENC_NotifyChange() function. If encoders are still too slow, incresse the divider setting in MIOS_ENC_SpeedSet(), e.g. use 4 instead of 2 (7 is maximum) No other changes are required, especially no hacks with a timer function or similar - everything is already provided by MIOS Best Regards, Thorsten.

Forgot to mention the Skill/Feature ratio: [tt] Required Skills ^ | ************* | *** | ** | * | * | * | * | * |* <--- your application is here |* +------------------------> Features [/tt]

[tt] [####--------------------------------] Required Programming Skills Newbie Expert [/tt] Best Regards, Thorsten.

Ok, finally I got the point. But wouldn't it be more consequential to display the current parameter assignment in full text (instead of the parameter number) when the item is selected (-> the selection button below the item is pushed)? I'm sure, that if the first Inc/Dec would be omitted for this particular menu item, it wouldn't take so long, until the first users would start to report a pseudo bug. Best Regards, Thorsten.

Could it be, that you mean a "slow" function which ensures, that even a fast encoder movement only increments/decrements a single step? Just press the SHIFT button and move the encoder! Alternatively, just don't move the encoder so fast for fine-tuning a parameter (wait ca. 0.2 seconds before moving to the next detent) - thats how I'm changing the Pa1 parameter, and it works great for me. Wilba: this is in conflict with the requirement to change multiple parameters the same time (e.g. CutOff with the right hand, Filter Decay with the left hand). I could add such a "encoder tick filter" function easily, but I would disable it by default, because I don't like it. Best Regards, Thorsten.

Wenn Du die uart_* Funktionen selber programmiert hast, solltest Du eigentlich den Unterschied zwischen einem String und Charactern (bzw. Bytes) kennen... Gruss, Thorsten.

Ok, you tried to build the application based on the old approach, but this doesn't work anymore as stated above. The make.bat file, the makefile generator + all the other tools which were used in older projects are obsolete - just start with the project setup in http://www.ucapps.de/tmp/ks0108_c_example.zip Best Regards, Thorsten.

Ok, so the coding examples under http://www.ucapps.de/mios_c.html are a good starting point. And the ready made Traktorizer Firmware of course (which only supports two decks so far I know, but switching MIDI channels for the additional decks shouldn't be so difficult - especially since the app is written in good readable C code) -> http://www.midibox.org/dokuwiki/doku.php?id=traktorizer_by_mte Best Regards, Thorsten.

Hehe ;) Yagosan: du kannst den PIC auch gerne zum Onkel Doc-tor schicken :) Doc: bitte den Flashinhalt vorher auslesen, in eine .hex Datei schreiben, und mir per email zuschicken. Gruss, Thorsten.

MIOS_MIDI_TxBufferPut() Achso, AVR und irgendeine Library, die Du irgendwo aus dem Web gefischt hast... Gibt es keine uart_putc() funktion, die bspw. das Versenden von uart_putc(0x90); uart_putc(0x3c); uart_putc(0x64); erlaubt? Schonmal in den Source code geschaut, wie uart_puts() die einzelnen Bytes versendet? Gruss, Thorsten.

And another huge & great looking MIDIbox LC has been born! :) MTE wrote:

Works fine at my side under DOS and Mac OS Could you please copy&paste the whole output of the make command? Best Regards, Thorsten.

Hallo, das liest sich so, als waere der Bootloader nicht richtig installiert. Denn wenn der PIC mit Spannung versorgt wird (TEST_CORE4 und 5), und der Quarz richtig angeschlossen ist (TEST_CORE2), dann sollte zumindest die LED am Tx Ausgang flackern (TEST_OUT1) Schicke mir mal den PIC + Rueckporto zu (meine Adresse findest Du im uCapps.de Impressum) Gruss, Thorsten. P.S.: Mit TEST_CORE5 ueberprueft man uebrigens, ob die Masse richtig angeschlossen ist, und es waere sehr unwahrscheinlich, dass die Diode (TEST_CORE7) defekt ist - zumal sie keine Auswirkung auf den MIDI Out hat. Eine Diode kann man uebrigens mit einem Multimeter testen (Widerstandsmessung: Durchlass nur bei richtiger Polung)

I think it's difficult to give you more explicit help, so long we don't know more about your skills. :/ Have you ever programmed in assembly language before? Then some (a lot!) modifications of MB64E application is the way to go. I could list the functions, but I wouldn't be able to hack down the code w/o testing it on the hardware. C skills available? Then it could be better to setup a new C based application which is perfectly tailored for your usecase (this might be much easier than doing changes in the MB64E application) Do you have a lot of time to get into the programming topic? Then we could start to give you more help into this direction. Or you are searching for a solution w/o doing the programming by yourself: then you will have to contact somebody, who did something similar in the past (unfortunately, not all customized projects are documented, only the forum search function will help to locate the people) Best Regards, Thorsten.

A pin-wise reassignment is simply not supported by the code, and it wouldn't be so easy to add such a function (especially to find a way which makes it easy for newbies to change assignments - just see, how confused you are already about the SR wise re-assignments) So, I think it's easier and less time-consuming to fix the solderings Best Regards, Thorsten.

Cur/CAs will be fixed with the next release. You mean a "peek" function, which is sometimes found on other synths to check the value. Normaly "peek" is activated with a special button, or button combination. I guess, that this would be better than ommiting the first Inc/Dec (where a second Inc/Dec could quickly follow if you move the encoder too fast) Best Regards, Thorsten.

I'm not sure if it depends on the BankStick. :/ Here an approach which should work under all circumstances: instead of hassling with SysEx requests and functions which are overwriting the previously written value, just define the MIDI channel directly in the CS_MENU_BANK_RestoreCfg function, and you are done :) Code: S_MENU_BANK_RestoreCfg movlw 0x05 ;; for channel 6 movwf CS_MENU_SID_M_CHN ;; used as SID master MIDI channel return ;;; rest of original code... [/code] Best Regards, Thorsten.

"B6 5B" is sent by the 7th AIN - seems that there is a problem with the pot connected to this input. Best Regards, Thorsten.

The MB808 variant of seq_enc.inc contains a function for a tempo encoder, which maybe can be re-used (I haven't tried it). The encoder pinning has to be added to the encoder table in setup_*.asm Some additional code is required to forward encoder movements of the additional encoder to the SEQ_ENC_Tempo function. This is usually done in main.inc, USER_ENC_NotifyChange Best Regards, Thorsten.

The MIDI channels are stored in EEPROM, but there is a sideeffect with the control surface handler. I assume, that you uploaded "setup_6581.hex" or "setup_8580.hex" instead of "setup_6581_without_cs.hex" or "setup_8580_without_cs.hex" The CS will load the MIDI channel selections of master and slaves from BankStick, and overrule the previously stored EEPROM settings Solution: open cs_menu_bank.inc, search for "CS_MENU_BANK_RestoreCfg", and add " return" below this label (the spaces are important) S_MENU_BANK_RestoreCfg return [/code] Thereafter rebuild the .hex files Or: upload a precompiled "*_without_cs.hex" variant (this will also disable the LCD, therefore the code modification is maybe the prefered solution) Best Regards, Thorsten.

I noticed, that the document is incomplete, because meanwhile we can select the channels of all three oscillators seperately. The change will take place with the next patch change. Here the update: g) F0 00 00 7E 46 <device-number> 0D 02 00 <OSC1 channel> F7 F0 00 00 7E 46 <device-number> 0D 01 00 <OSC2 channel> F7 F0 00 00 7E 46 <device-number> 0D 00 00 <OSC3 channel> F7 Change the MIDI channel Value 00 (for Channel #1) .. 0F (for Channel #16) is expected. Note that the channels of the oscillators can be changed seperately. In normal cases, all channels should be set to the same value. The values are stored in EEPROM, accordingly there must be a delay of at least 5 mS between each SysEx command, otherwise data gets lost The change will take place with the next Patch selection. E.g., you could send a program change (e.g. C0 <patch>) after the SysEx commands. Example for configuring MIDI channel #16 on SID1: F0 00 00 7E 46 00 0D 02 00 0F F7 F0 00 00 7E 46 00 0D 01 00 0F F7 F0 00 00 7E 46 00 0D 00 00 0F F7 C0 00 [/code] Best Regards, Thorsten.