TK.

Hi Nenad, the unused DIN pins have to be connected to +5V via 10k resistors --- if you built the DIN module completely, these "pull-ups" are already available so that you don't need to take special care for the button inputs. Best Regards, Thorsten.

Hi Serum, sure, this graphic LCD can be connected to the core module. But it requires another driver. There are three possibilities: either you try to modify the existing driver so that it communicates with the HD61830 (I think that I can help via remote), or somebody with programming skills buys a HD61830 and helps us, or you lend me the LCD so that I'm able to setup the routines @home. Btw.: the MIDIbox NG will come with a three-layer driver model, the 1st level accesses the dotmatrix or graphic display directly, the 2nd level provides some API functions between the display and user code, and the 3rd level will allow the user to write something to the LCD by accessing a SRAM buffer. This will be the most flexible solution, because for different LCDs just only the 1st level routines (about 100 bytes) have to be adapted; everything else will be compatible and can be reused. Best Regards, Thorsten.

Hi Dave, Congratulations - the IBK10 is one of the best controllers designs! :) well, concerning the MB64seq: it wouldn't be a big job to integrate a feature which allows you to control the "pot values" from external via CC. But a LCD and at least 8 buttons have to be added beside of the core module, because without these control elements playing with the MB64 will make no fun. Currently the SysEx dump cannot be edited by Serge's software, since it requires a totally different editing concept... however, the concept of MB64seq isn't to replace a groovebox or sequencer software, the idea behind this box is to allow direct control of notes/CC patterns, which mostly results into more creative and dynamic sequences Best Regards, Thorsten.

The old versions can be found here: http://www.ucapps.de/midibox/midibox_plus_pcb_dave_v2.zip http://www.ucapps.de/midibox/midibox_plus_pcb_shum.zip http://www.ucapps.de/midibox/midibox_plus_pcb_martin3.zip they have been temporary removed from the website since they require some additional docs concerning the (slightly) modified hardware. Best Regards, Thorsten.

Unisono is a feature especially for the users who want to use 2 SIDs in stereo configuration. It already can be realized by detuning the pitch, but the Unisono button will make it easier. Yes, also single oscillators will be controlable over different channels or in split mode, this has already been prepared - I only need a control surface to select all these already implemented options. ;-) I won't publish a list of required modules, etc. before February, because the specs have not been frozen yet and could be changed when I begin to play with the alpha version and notice that something is missing for a perfect interaction... Best Regards, Thorsten.

Hallo Jack, Ich benoetige keinen Master-Fader, ausserdem muesste ich dafuer eine zweite MIDIbox MF bauen (jede MBMF kann nur 8 Fader bedienen), was ich natuerlich vermeiden moechte. ;-) Zum Anwaehlen der restlichen Parameter, sowie zum Senden von sogenannten Double-Note-Events, mit denen man die zusaetzlichen MIDI Remote Funktionen von Logic bedienen kann. Man kann natuerlich auch beliebige andere Events (oder SFB-Funktionen) darauf legen, wie bspw. die SFBs fuer das Bankswitching (so kann man mal schnell ein anderes MIDI-Geraet/Programm ansteuern...) es befindet sich auf der rechten Seite unter den 32 Mini-Buttons Ich werde wohl Schablonen ueber die Tasten legen, weil ich mit dem Controller ja nicht nur eine LC emulieren moechte ;-) Gruss, Thorsten.

Nein, das kann der SID leider nicht. Stattdessen veraendert man einfach den Sustain-Level der Huellkurve, das wirkt fast genauso ;-) Best Regards, Thorsten.

What did you finish up to now? Btw: this posting contains some answers to common problems: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1041817688 Best Regards, Thorsten.

No, this isn't possible... two cores are required. Best Regards, Thorsten.

Yes, it's already possible to connect up to 16 LEDs for each ring/bar. The patterns are free definable (see http://www.ucapps.de/midibox/mk_syx.zip , the midibox16e.ini sample file). The LC emulation will offer the same features (and a little bit more ;-)) Best Regards, Thorsten.

I will continue with the MIDIbox NG/LC when I get the panel from Schaeffer, thereafter it could get about one or two weekends until the new box is ready for the public. As far as I know there is no functional difference between LC and MC, just only the device IDs are not the same to prevent a connection between Logic and MC ;-) Best Regards, Thorsten.

Yes, thats possible with the example Meta event which is already included in v1.909: ;; this example sends a registered value, it allows you to increment/decrement a program change: ;; first value: Fn - n stands for the selected MIDI channel ;; second value: if 00: decrement, 01: increment, 02: send without increment/decrement ;; third value: decrement/increment: don't care; else the value which should be sent and stored into the internal register ;; necessary definitions in midibox16.ini: ;; 1.1 = F0 00 7F @OnOff ;; 1.2 = F0 01 7F @OnOff ;; 1.3 = F0 02 7F @OnOff

Here a short summary which should answer all your questions :) The interaction between the control surface and the external SID cores will happen over common MIDI connections. Every core gets it's one device number, so that up to 16 cores can be accessed. It will be a one-way connection between MIDI OUT of the control surface and the MIDI INs of the other cores. The MIDI OUTs of the external cores will not be used, since every slave is under direct control of the master core. The SysEx commands which are necessary for this configuration have been introduced in firmware release v1.4 and they are already used by the Java editor - it's possible to send a whole sound patch to the EEPROM in between 100 mS (F0 00 00 7E 46 <device-number> 02 <patch-number> <256 bytes of dump data> F7), and to directly change parameters of the dump without writing it into the EEPROM in between 2 mS (F0 00 00 7E 46 <device-number> 06 AH AL <value> F7). The SID module which is connected directly to the control surface will be handled as virtual MIDI device (or in other words: as a VSTi ;-)) so that you don't see a difference between externaly and internaly controlled SID When you select between different SIDs with the appr. button, you just select the device number... The BankStick which is attached to the control surface stores sound patches for all SIDs. It will be possible to select different patches for several SIDs. When you select a sound patch for an external SID, it will be transfered in between 100 mS to the selected SID. Maybe it will also be possible to access up to 8 BankSticks from the surface, since I noticed that the Microchip EEPROMs offer 3 chip select lines (= 8 addresses) It will also be possible to use the surface as common MIDI controller for VST instruments or whatever since there is no difference between controlling a SID slave core or any other MIDI device. Just assign your favourite MIDI events to the "assign" banks in the OSC and ENV section... I think that more than one assignable bank can be realized on the following way: hold the assign button and select one of 5 banks with the buttons below the LCD, or select it with the jog-wheel beside of the LCD. Some words to the playing modes: Single every SID will get it's own sound patch and can be assigned to the same or to different MIDI channels. Unisono also known as phat mode ;-) --- all SIDs are assigned to the same MIDI channel and will play an identical sound. Only the finetune value will be different, which results into fat leads Split SIDs will be controlled over the same MIDI channel, but will get different sections on the keyboard, so that you can i.e. play different percussion sounds on one channel or play a bass and a lead sound with two hands About variations (i.E. low-cost versions, different displays or whatever): the final surface will already be very flexible, so that it can be used with different button, LED, LCD and encoder configurations. It's planned to publish the source code for the "surface control handler" in form of a MIDIbox NG PlugIn, which can be modified for own requirements and can be uploaded over MIDI. On this way you can customize the whole surface also for other applications. I.e, it can be quickly turned to a completely different controller for a different instrument in between 1 minute :) Best Regards, Thorsten.

Unter diesen Umstaenden wuerde ich auf LED-Digits nicht verzichten. Dazu benoetigst Du keine einzelnen LEDs, es gibt die Digits auch fix und fertig bei Reichelt zu kaufen: SA_08-11_rt Das MTC-Beispiel unter Concept->Test Programs mag zwar kompliziert aussehen, im Grunde laesst es sich aber Plug-and-Play maessig integrieren. Mit dem PIC18F wird wie gesagt alles einfacher und kompakter; fuer diese Plattform werde ich Beispiele bereitstellen, die auf dem "MIOS" basieren (ein selbstgebasteltes Betriebssystem, das die grundsaetzlichen Verwaltungsaufgaben fuer MIDI-Anwendungen uebernimmt). Uebrig bleibt dann im Grunde nur noch die Codierungstabelle fuer die LEDs unter contab_l.inc. Die Digits koennen dann jederzeit mit einfachen Registerzugriffen beschrieben werden: movlw 0x01 movwf LED_DIGIT0 movlw 0x02 movwf LED_DIGIT1 movlw 0x03 movwf LED_DIGIT2 movlw 0x04 movwf LED_DIGIT3 den Rest uebernimmt das Betriebsystem. Einfacher geht es dann glaube ich nicht mehr. ;-) Gruss, Thorsten.

Hi, yes, Windows XP requires the win2000 driver as far as I know, otherwise the access to the serial interface is too slow, so that the C-charging unit of JDM (than faster the pulse, than higher the voltage) cannot be "pumped" to the required voltage levels. Best Regards, Thorsten.

Thanks for the input, I've added the link to the list. However, it seems that Schuricht still offers the best prices for encoders in small quantities, although the other components in the online shop are expensive compared to Reichelt (but Reichelt has no encoders, hrmpf :-/) It seems that I'm able to order there, I just wrote them that I'm a freelancer (although I've no business...) and they granted my request ;-) Best Regards, Thorsten.

Sounds interesting - the handling would be similar to a jog wheel known from videorecorders (e.g.). Such a feature could be realized with a Meta event (requires programming skills and a MIDIbox of course ;-)) Best Regards, Thorsten.

The files can now be found here: http://www.ucapps.de/tmp/mbsid_19inch_Control_Surface_NorthernLight.gif http://www.ucapps.de/tmp/mbsid_19inch_Control_Surface_NorthernLight.fpd a nice solution for a bigger panel :) Best Regards, Thorsten.

Yes! :) Best Regards, Thorsten.

I've changed the layout again after I got a suggestion for the parameter structure on the display by Jan aka Captain Hastings. It makes sense to display 5 parameters in a row according the number of encoders in the OSC and ENV section. It possibly also makes sense to provide a minimal version with 5 encoders instead of buttons below the display. I've also added a new option for the multi-SID solution: "Single", "Unison" and "Split". The new .fpd file can be found here: http://www.ucapps.de/tmp/mbsid3.fpd For those who are interested: feel free to make your own modifications and introduce them here! :) Best Regards, Thorsten.

Ian: I don't want to support ports, because this would decrease the ergonomic handling. It's very important that you can switch between different oscillators, SIDs, etc. without readjusting the pots. However, rotary encoders are not much more expensive, and the LED rings can be left out, because when you turn on an encoder, the value will also be displayed by the LCD. SID release V1.4 LCD support: it shows the bank name, patch number, MIDI channel and device number - nothing else... ;-) Ilmentator: It's a great idea just to re-use the C64 case. I've experimented a little with an old C64-I, here the result: Btw.: as you can see the features are not frozen, and the panel doesn't include all the necessary screw holes yet. Therefore the following .fpd file is only for your own first experiments: http://www.ucapps.de/tmp/mbsid2.fpd There are a lot of expensive engraving elements at the panel, which I will remove for my final order - I will just add the labels with a foil or something else. Best Regards, Thorsten.

Ich bin mir nicht sicher, ob jemand das erweiterte Layout jemals ausprobiert hat, jedenfalls habe ich noch keine Klagen gehoert ;-) Ab naechste Woche wird es uebrigens ein fertiges PCB in Mikes Shop zu kaufen geben. Der Preis liegt bei ca. 7 Euro... falls Du also auf Nummer sicher gehen moechtest, waere das evtl. eine Alternative. Gruss, Thorsten.

Did you try to contact the distributor of Alps in Milano? http://www.eccabacus.it/ Best Regards, Thorsten.

Correct - I would also build this simple circuit on a vector board, and with the upcoming v1.910 release the performance of MIDIbox Plus is exactly the same like for the MBHP based designs (the preliminary firmware is already available by request). Btw.: the schematic is perfect now :) Best Regards, Thorsten.

Thanks again for the applause - for myself it's the same, I can't wait to see all those LEDs flashing and to get a much better control over my SIDs :) But I won't be able to begin with the surface before february, since the MIDIbox LC/NG has a higher priority (I will receive the panel possibly next week). I also haven't found a nice case yet (dimensions are 25 cm x 20 cm, resp. 10" x 8"), and finally my holidays are over and a lot of work is waiting in the office... :P Yes, the control surface will only be available for the PIC18F core, because the application requires a lot of text data for a detailed menu structure which doesn't fit into the memory of a 16F877. Since the price of a PIC18F is nearly the same, this should be ok. The surface can control one SID module directly, each additional SID requires an own core (PIC16F or PIC18F...) LCD: I'm not sure if I will use a 16x2 or 20x2 - I will decide this when I start with the menu handler Best Regards, Thorsten.