TK.

Hi Dave, yes, you are right. Pressing the third button should save the patch, and it should especially not hang up. Not sure if this was an imperfection in v1.7a (nobody reported it before), but could you please try the same with v1.7303beta? -> http://www.midibox.org/forum/index.php?topic=6098.0 #B stands for Bank, #P for patch It only works properly when a BankStick is connected Best Regards, Thorsten.

Ok, one last feature (the last version was not cool enough ;-)): [tt] o each second LFO now provides a Sample & Hold functionality when switched to random mode. LFO2, 4 and 5 hold the waveform of LFO1, 3 and 5 for each period run. Example: - in the modulation matrix, enable LFO2 modulation for the Pitch of OSC1 -> this is the S&H output - set LFO2 to random mode, Rate=70, Depth doesn't matter - set LFO1 to sine or random mode, and vary Rate and Depth [/tt] -> http://www.ucapps.de/mios/midibox_sid_v1_7_303beta12.zip Best Regards, Thorsten.

Hi Julian, I know the anoying delay bug, it was fixed in one of the last v1.7303 releases. The interesting point is, that you are the first guy who reported this ;-) Random function: you are absolutely right, random gets powerful with Sample&Hold, therefore I've added this feature to v1.7303beta12 -> http://www.midibox.org/forum/index.php?topic=6098.0 Best Regards, Thorsten.

Frage lieber Admir, ich denke mal, dass es in seiner Gallerie am besten aufgehoben ist. Aber Du kannst hier dann gerne einen Link posten Gruss, Thorsten.

Hi David, the table lists an ON and OFF event for each individual input: [tt] [MIDI_OUT] ########################################## # Pin # On Evnt # Off Evnt # Behaviour # ########################################## 1 = 90 30 7F 90 30 00 @OnOff 2 = 90 31 7F 90 31 00 @OnOff 3 = 90 32 7F 90 32 00 @OnOff ...etc... [/tt] The "90" stands for "Note On at Channel 1", if you want to send a Note On over channel 2, then just replace 90 by 91 It's hexadecimal coding, and we are counting from zero. Means: 0...9 = MIDI Channel #1-#10, A = MIDI Channel #11, B = #12, C=#13, D=#14, E=#15, F=#16 MIDI Note 60 is hex 3C, if it should sent over Channel 3, then write: [tt] 5 = 92 3C 7F 92 3C 00 @OnOff [/tt] Best Regards, Thorsten.

Nicht unbedingt - wenn die Taster erstmal durch die Bohrungen passen (was wirklich in eine ziemliche Fummelarbeit ausarten kann), heize ich mit dem Loetkolben die Loetstellen nochmal an, so dass sich die Taster zentrieren lassen. Diese Prozedur wiederhole ich dann ein- bis zweimal, bis es bei allen Tastern passt. :) Gruss, Thorsten.

Hi John, thanks for the feedback! Don't hesitate to publish your application once it is finished, it will be at least a nice inspiration for other people :) Best Regards, Thorsten.

The upcoming release has reached it's final beta state: feature freeze. Now the time has come to check if the old functions are still working. A snapshot can be downloaded from this location: http://www.ucapps.de/mios/midibox_sid_v1_7_303beta11.zip One of the last feature is the constant time glide function, which was discussed here: http://www.midibox.org/forum/index.php?topic=6044.0. It can be activated with sound engine option bit #2, e.g. CFG menu, select OPT=4, or JSynthLib, click on flag #2 More details are listed in the CHANGELOG.txt file Best Regards, Thorsten.

Concerning the control extension I've some bad and good news. The bad news is, that the required code won't fit into the MBSID release anymore, even if I would spent some more effort in code optimizations (which I already did several times in order to realize the new 303 features) But the good news: Not for the next months, but propably next winter I will start with a totally overworked version (V2) which will run on a PIC18F4620 (64k device, pin compatible to PIC18F452). Until then I will collect ideas for the new V2 engine. General requirement: the main panel will be identical (I don't want to throw away my own one), but there will be more sound parameters, a stereo option, an extensive AOUT modulation matrix, a trigger matrix, a special "wavetable" for note sequences, a second MIDI Out for the slaves, etc.. etc.. and especially a 303ish control extension, which will look like a keyboard, and which will support several recording modes. I cannot give more details, since they are changing from time to time ;-) Best Regards, Thorsten.

Hi Gideon, I'm happy that this new application helped. And thank you very much for the donations! :) Raphael: I will ask Twin-X, the icon vanished during the last forum software update Best Regards, Thorsten.

Super, dann sollte ich auf meiner Page den Roland Treiber vor dem Yamaha Treiber erwaehnen. Das geht gerade nicht so ohne weiteres (vom Laptop aus...) - doch wo bleibst Du denn haengen? Warum klappt es nicht, die Zeile im main.asm zu aendern, und die Applikation neu zu assemblieren? Gruss, Thorsten.

As always, you guys are requesting things which are not possible, please give me my freedom to say "done" without spending more nights in coding of a feature, which will propably only be used by a small number of people. I'm very happy with the current implementation, and I can live with the limitation, that ENV2 will not be available in this mode. Thinks which make it impossible: code consumption, register consumption, availability of free CCs (to modify the curve), time to update all the tools (e.g. JSynthLib) However, I can take a seperate curve feature for portamento into account for the MBSID V2 engine Btw.: it doesn't work with tables, but with an algorithm which calculates the bended curve in realtime (a very dynamic thinky, once you modulate the curve parameter with the wavetable sequencer :) the sound engine option CC has 7 bit, 2 are currently used (TB303 and filter interpolation), 5 are free - so, the third one will be used to route ENV2 to portamento. I think this is a flexible solution, no? :) Best Regards, Thorsten.

Ja, wenn Du den to-COM Treiber verwendest, ist die ID 100 richtig. scheinbar funktioniert der COM Treiber vom Yamaha nicht richtig auf Deinem System. Das habe ich schon des oefteren gelesen, deshalb gibt es noch zwei alternativen von Roland und Kawai. Probiere die mal aus Gruss, Thorsten.

Maybe somebody wants to try to re-program the floorboard on a C based MIOS application? http://www.ucapps.de/mios_c.html It's simple! Best Regards, Thorsten.

Sorry, habe beim "Post"-clicken noch aufgeschnappt, dass Du ja ein AIN Modul gebaut hast. Umso einfacher: klemme alle ungenutzen analogen Eingaenge an Masse wie unter http://www.ucapps.de/mbhp/auaimbctc.pdf beschrieben, und lade die MB64 applikation auf. Falls Dir das Klemmen zuviel aufwand ist, muesstest Du die Applikation halt wie oben beschrieben aendern (in diesem Fall wird DEFAULT_MUX_ENABLED jedoch auf 1 gesetzt) Gruss, Thorsten.

Hallo Kay, Du koenntest die MIDIbox64 Applikation neu konfigurieren, einfach main.asm oeffnen, DEFAULT_NUMBER_POTS auf 1 setzen und DEFAULT_MUX_ENABLED auf 0 Danach ein neues main.hex bauen wie unter http://www.ucapps.de/howto_tools_mpasm.html beschrieben Die "Ausgabeelemente" (LCD/LEDs) sowie die Buttons verhalten sich passiv, hier musst Du nichts aendern Gruss, Thorsten.

Hallo, irgendetwas stimmt mit den Verbindungen zwischen Core und LCD Modul nicht, evtl. gibt es sogar einen Kurzschluss. Checke mal in Ruhe die Daten und Control Leitungen durch. Gruss, Thorsten.

Anmerkung: bei Loetarbeiten an den verklebten LEDs muss man hoellisch aufpassen, dass man nicht allzulange mit den (giftigen?) Daempfen in Beruehrung kommt. Sie brennen vor allem in den Augen. Am besten macht man das im Freien (was im Winter jedoch etwas schwierig wird ;-)) Gruss, Thorsten.

Hi Jesper, this: if (ccValue < 0x7e){ ccValue++; ccValue++; break; } else{ break; } [/code] can be simplified as: [code] ccValue += 2; if( ccValue >= 128 ) ccValue = 127; and decrements with: ccValue -= 2; if( ccValue >= 128 ) ccValue = 0; [/code] Checking for ccValue >= 128 is not an error - ccValue is an "unsigned char" (an 8bit value), which means, once there is an underrun, the resulting value will be <= 255 Best Regards, Thorsten.

Hi, with TL's patch manager (-> http://www.automatic-brain.de/midibox/) the upload is normaly not a big deal, since it waits for a response from the MBSID before sending the next patch. But on a Mac you have to adjust the delay between two SysEx messages (patches) manually. A good starting point is 500 mS. If you are able to run a MIDI monitor in parallel, check that each patch gets an acknowledge message (.... 0F F7). If an acknowledge is missing, then the delay is too short. Best Regards, Thorsten.

Hi Kokoon, it's not so easy to demonstrate all the possibilities, since there are 127*127 different possibilities (attack rate * curve parameter). However, I've created a new demo where at the first half a linear curve is used, and at the second half a bended curve. -> http://www.ucapps.de/tmp/mbsid_constant_slide4.mp3 not exactly, I've mapped the output of ENV2 to the input of the portamento routine. The amplitude of ENV2 is scaled by the difference between the previous and the target frequency. By doing so, we always have a constant rate (-> the attack rate), and the shape can be freely bended to the negative and positive direction without changing any code :) For the case that you don't know the ENV curve feature, here some older snapshots (in my examples, I only used the attack phase, decay is 0, sustain is 127, release is 0) Best Regards, Thorsten.

There are some other possible connection errors, which you've propably not tested (e.g. signals against the 5V line). However, in order to simplify the debugging procedure, I've written a new test program which simplifies this: http://www.ucapps.de/mios/srio_interconnection_test_v1.zip from the main.asm header: [tt] ; A CORE->DIN/DOUT Module Interconnection Test ; ; This application allows you to check the interconnections to the DIN and DOUT module ; with a multimeter. You can control the SR/RC/DO pins by sending a Modulation Wheel ; event to your MIDIbox Core - just connect a keyboard or use ; MIDI-Ox (View->Control Panel) ; ; By default all unselected pins are 0V, except for the CS# pin which is 5V ; ; The Pins are mapped to following Modulation Wheel Values: ; ; # 0: Pin CORE::J8:DO and DOUT::J1:DO = ca. 5V ; # 1: Pin CORE::J8:SC, CORE::J9:SC, DOUT::J1:SC, DIN::J1:SC = ca. 5V ; # 2: Pin CORE::J8:RC, CORE::J9:RC, DOUT::J1:RC, DIN::J1:RC = ca. 5V ; ; The pin names are also visible on LCD (if connected) ; ; If you measure a voltage much less than 4.8V (e.g. < 3V or even 0V), then ; there is either a short circuit or a missing connection between ; the signal lines ; ; If a certain shift register is not working, you could measure the ; SC/RC voltages directly at the pins of the 74HC595/74HC165, please have ; a look into the schematics: ; http://www.ucapps.de/mbhp/mbhp_doutx4.pdf ; http://www.ucapps.de/mbhp/mbhp_dinx4.pdf ; ; The J9:DI pin can be tested with the MIDIO128 application, ; once you've ensured that SR/RC are working ; Each digital input of the DINX4 module has to trigger a single MIDI event [/tt] Maybe a bad soldering joint? (waggly connection) The new program should help you to identify this. Best Regards, Thorsten.

Hi Matteo, this is propably the field is still in edit mode (white background), and therefore the value hasn't been taken. If this is the case, you have to click on another field first, before pushing the update button (it's not my fault, but just the behaviour of the Java GUI interface) However, the easiest way is just to move the cursor one field down- or upwards. Best Regards, Thorsten.

After tinkering with the ENV2 mod, I think that the simplest solution (linear slide, suggested by Kokoon) is sufficient, see following examples: http://www.ucapps.de/tmp/mbsid_constant_slide3.mp3 * at the beginning a slide with linear curve * thereafter with "negative curve" * at the end with "positive curve", which fits best with a cap charging curve The differences are so small, that it isn't really worth the effort to integrate the ENV2->portamento path into the engine (it consumes some resources...). I will make this feature selectable with sound engine option #3, so that it's possible to switch between the two different behaviours :) Best Regards, Thorsten.

Hi David, yes, even the PIC16F877 based solution provides a configuration mechanism, which allows you to alter the channels (and even the MIDI events which are sent). Details can be found in the mk_syx_midio128 script, which can be downloaded from the MIDIO128 page Best Regards, Thorsten.