TK.

No, the AINX4 module itself should still be supplied by the core module. Only the analog inputs can be optionally connected to other voltage sources. If you've a source which outputs 0-5V, just connect the output pin to one of the analog inputs.... don't forget to join the grounds! Best Regards, Thorsten.

Hi Christoffer, my suggestion is to build at least one SID core with the PIC16F as a reference. Since the current JDM programmer possibly needs some modifications to supply the PIC18F, the ramp-up of the new design can be pretty difficult w/o electronic knowledge. Hope that it will get easier when enough experienced people tried it. LTC: it's only an electronic extension, sure it works also with the SID. You can also connect the J11:MI and J11:Vs pins of the cores w/o MIDI interface to J11:MI/J11:Vs of the core with MIDI interface together. On this way the MI pins acts as "MIDI Through". Additional amplifiers (74HC00) are not required as long as the additional cores are not stuffed with optocouplers. For a better understanding: J11:MI is the digital MIDI In which goes to the Rx pin of the PIC. It can be used to supply the Rx (digital MIDI In) pin if no optocoupler is connected, or to forward the MIDI stream which goes through the optocoupler (digital MIDI Through) J11:MO is the digital MIDI Out which comes from the Tx pin of the PIC. It can be used to chain MIDI modules (MIDI Out 1st core -> MIDI In 2nd core). This method is not supported by the SID module, because it requires an internal MIDI Merger. If you wire the MI or MO pin from one to another core, the ground pins (J11:Vs) have to be connected also. LEDs can be connected to both pins: J11:MI for MIDI In LED, J11:MO for MIDI Out LED - but they require an amplifier which can be found on the LTC module. Just try it... :) Best Regards, Thorsten.

No there isn't. But note that the next MB64 Release (V1.0 final!!! ;-)) will support 64 buttons, so that 2 * DINX4 modules make sense (the modules can be chained). Best Regards, Thorsten.

The new release comes with several bugfixes in the Note handler (overlapped notes are tied correctly now), in the MIDI clock synchronization and in the SysEx dump structure. http://www.ucapps.de/midibox/midibox64seq_v0.91.zip It features also a new submenu with presets for a quick configuration: N1/N2/N3/N4: Track 1-4 send notes on MIDI Channel 1, 2, 3, 4 C1/C2/C3/C4: Track 1-4 send controllers on MIDI Channel 1, 2, 3, 4 N1/C1/N2/C2: Track1/3 send notes on channel 1/2, track 2/4 send controllers on channel 1/2 N1/C1/C1/C1: Track 1 sends notes on channel 1, track 2-4 send controllers (Track 4 with Ping Pong effect) Drums: Track 1-4 trigger drum samples (Bass Drum, Snare, Closed/Opened HiHat) on MIDI Channel 10 Gater Fx 4Chn: Track 1-4 send CC#7 controllers for a nice gater effect on Channel 1-4 Transp.Crazy1: Track 1-4 send notes on Channel 1 in various sequencer modes (Normal/Transpose/T+Hold/Arpeggiator) at the same time Transp.Crazy2: same like above, but with additional dividers and PingPongs Enjoy! :-) Best Regards, Thorsten.

Servus, wirklich gute Buecher ueber Microcontroller kann ich leider nicht empfehlen, aber gerade fuer den PIC gibt es zahlreiche Seiten im Web, die interessante Informationen auch fuer Anfaenger liefern. Einen Einstieg findest Du auf dieser Seite: http://www.piclist.com/techref/piclist/begin.htm Und hier befindet sich ein sehr gut beschriebenes Einsteigerprojekt: http://www.piclist.com/techref/piclist/biketut/index.htm Ansonsten lohnt es sich vielleicht, mal im Archiv der Unibibliothek nach alten Elrad und Elektor Heften ausschau zu halten, in diesen Elektronikzeitschriften werden die Grundlagen meist leicht verstaendlich und nicht zu theorielastig erklaert. Gruss, Thorsten.

cool! :) Best Regards, Thorsten.

This has to be evaluated... since the PIC18F comes with much more RAM, a second MIDI buffer could be realized like on the standalone MIDI Merger, this would decrease the latency to 320 uS - 960 uS on usual cases (when no SysEx data is received/sent) Best Regards, Thorsten.

Hi Ilmenator, a nice application for the filter! Hope that you will publish the final source code, so that other people can use it as template to solve their problems :) I don't expect that the second event is sent by the filter. Maybe from the StudioMix? Does it come with a MIDI Merger? This would explain why the NRPNs (the "used" values) will not be forwarded... how did you connect the MIDI INs/MIDI OUTs? Are you using 2 MIDI INs on your PC? Best Regards, Thorsten.

Hi Christoffer, thats correct, I've disabled the MIDI merger in this firmware so that the SID module behaves like a common MIDI synthesizer. A temporary workaround: remove the optocoupler of the SID core module and connect J11:MO of the MB64 core with J11:MI of the SID core and connect the J11:Vs pins (ground) of both cores together. On this way the MIDI stream which is coming out of the MIDIbox64 will be routed to the MBSID and your PC. I will check in the next days if an activated merger causes performance problems in the MBSID firmware. Best Regards, Thorsten.

That's really weird - I've no answer (yet) :-/ Best Regards, Thorsten.

Hi, I compared the LCD drivers of both firmwares and found one major difference. I'm unsure if it is really the reason, so please could you test this one: http://www.ucapps.de/midibox_sid/midibox_sid_v1.1b.zip Best Regards, Thorsten.

Finally the first beta version of MIDIbox64SEQ is available: http://www.ucapps.de/midibox/midibox64seq_v0.91.zip A brief description for the beta testers: The first version doesn't come with a mk_syx script, therefore all parameters have to be configured direcly at the box. A LCD, at least 8 buttons and a lot of pots (of course) are required. The Left/Right/Exec buttons have the same functions like on other MIDIbox versions. The "snapshot" button is used to start/stop the sequencer, to select the track and layers in the submenues, and so on... so try this button within every submenu to test the purpose. Every pot-row controls one track. 4 independent tracks are available. Each track consists of 3 layers which can be assigned to: Note Number, Velocity, Gate Length (on Note Events) CC Number, CC Value, Gate Length (on Controllers) 1st Parameter, 2nd Parameter, Gate Length (on other events) With the functional buttons F2-F4 the layers A, B, C can be selected. All pots will change their "purpose" on this way. A Soft-Takeover (Snap) function prevents parameter jumps. When you type the F1 button shortly, the Soft-Takeover function will be disabled until a new Layer is selected. This is fine for quick parameter changes. When you hold the F1 button and turn a pot, all parameters of the same row will be changed. On this way you can quickly select a note, velocity, gatelength, CC, CC value, ... for the whole row with one pot. Now the configuration (press the Exec button and go through the main menu): Select Bank: used to select another bank (BankStick required...) MIDI Learn: used to assign a MIDI Event to the Tracks/Pots Track Mode: can be selected for each track seperately: off (no MIDI Event will be sent by the track), "Normal": (nothing to say), "Transpose" (an external MIDI keyboard can be used to transpose the notes), "Transpose+Hold" (same with hold function), "Arpeggiator" (like Transpose, but poly), "Arpeggiator+Hold" (same with hold function), "Controller" (the whole pot row will not be clocked by the sequencer and can be used like a on as common MIDI controllers) Direction: can be selected for each track seperately: Forward, Backward, Ping Pong, Random. The Random function requests the spare pin of the MBHP Core module (J14) for the direction. If this pin is open, the status is random. You could also connect a switch, a waveform generator or something similar to this pin for nice sequencing effects. :) Or you can just tip your finger on it ;-) Clock Divider: can be selected for each track seperately: BPM/1, BPM/2, BPM/4, BPM/8, BPM/16 Track Length: can be selected for each track seperately: 1, 2, 3, ... 16 Layer Assignments: 12 Layers (4 Tracks * 3 Layers) have to be assigned to the sequencer functions: Note/Ctrl. Number, Velocity/Value, Gatelength BPM: values between 48 and 250 are possible. Select speed "47" if the sequencer should act as MIDI clock slave. MIDI Config.: MIDI Merger on/off, MIDIbox-to-COM on/off Send SysEx: allows you to send a SysEx dump in order to save the setup Limitations: Layer C contains only one value for the whole row (Layer A, B: 16 values). This restriction was necessary due to limited RAM - in the PIC18F452 version this limitation will not exist. Workaround: assign a static sequencer function to Layer C. If the track should play a drum, just assign the note number to layer A, velcoity to layer B and the gatelength to Layer C (-> gatelength never change). Or if you want to sequence a MIDI controller, assign the CC Value to Layer A, the gatelength to Layer B and the CC number to Layer C (-> CC number never change) the sequencer only play the type of MIDI event which is assigned to the first pot of every track. However, this doesn't really hurt ;-) the pot values are only stored in EEPROM when you enter the SysEx menu. So go into this submenu before you switch off the box. This circumstance will be solved in the next version with a SFB the next version will also support 64 LEDs and a 4x16 LCD Happy betatesting! :-) Best Regards, Thorsten.

Servus,

Hi, sounds strange! Does your LCD work with V1.0? http://www.ucapps.de/midibox_sid/midibox_sid_v1.0.zip Best Regards, Thorsten.

Due to a lot of requests and documentation problems, next weekend I will clean up the MIDIbox64, MIDIbox16E, MIDIbox MF firmwares. Beside of the known features the new versions will provide: 64 Buttons (2 DINX4 modules) 64 LEDs (2 DOUTX4 modules) Device Numbers a new SysEx dump structure (sorry, Serge!) The motorfader and sequencer part will be removed from the MIDIbox64 firmware. Tomorrow a first version of MIDIbox64SEQ will be available with a new handling and new functions: 4 Tracks with 3 Layers (for Note Number/CC Number/Velocity/Gatelength/...) Seperate Transposer/Arpeggiator for each Track independent clock divider and direction flags (Forward/Backward/PingPong/Random) for each Track Pot-Rows can also be assigned to common controller functions, so that you can control the parameters of your synthesizers and play sequences with one MIDIbox at the same time A later version will also provide 64 LEDs, so that every pot has it's own LED. Best Regards, Thorsten.

Hi, When will a first prototype of the MidiBox NG be ready? I will start with the MIOS in my winder holidays - so the first release should be available in January. Best Regards, Thorsten.

Mist, das wollte ich eigentlich einbauen, habe es aber vergessen. Demnaechst wird es also einen "temporaeren Bankswitch" geben, mit dem man mal auf die Schnelle eine andere Bank einblenden kann. Gruss, Thorstem.

Problematisch ist nur, dass meine "vintage" MIDIbox64 MF gar nicht mehr existiert, ich habe sie ja mittlerweile zu einer MIDIbox MF (mit neuem MF Modul) umgebaut. Deshalb kann ich das alte Design auch nicht mehr supporten (sprich: debuggen, falls es mal zu problemen kommen sollte). Hinzu kommt, dass aus der v0.35pre bereits der Motordriver rausgeflogen ist, die dadurch freie gewordenen Register werden nun von einem neuen Feature verwendet. Die zusaetzliche Hardware fuer eine MIDIbox MF ist gar nicht mal so teuer. Auf ein zweites Display kann man erstmal verzichten, die Spannungsversorgung kann vom ersten Core abgezweigt werden (-> Port J2), die MIDI-Schnittstellen lassen sich ueber den J11 Port verketten, spaeter ist ein MIDIbox-Link moeglich, so dass noch nicht mal zusaetzliche Buttons fuer das Bankswitching benoetigt werden. Uebrig bleiben: ein PIC, ein Quarz, zwei 33pF Kondensatoren, drei Pull-Up Widerstaende an Pin RA4, RC3 und RD1, und das MF-Modul. Das laesst sich auch prima auf Lochraster aufbauen. Im Endeffekt betragen die Mehrkosten also gerade mal 15 EUR :-) Gruss, Thorsten.

Hi Lo, it's really difficult with the specs for power supplies. Sometimes the effective voltage is given, sometimes not. Sometimes the voltage under load, sometimes not... however, the only interesting attribute is the output voltage under a current drain of 1A. If all motors are in standby mode, the current load is less than 1 mA, that's the reason why you see a higher voltage (before the LM317) Unfortunately the LM317 has to consume the difference voltage between the input and output. The result is heat. In fact the LM317 will get hotter with higher voltages, so if you have the option, take a power supply with 12-14V AC Best Regards, Thorsten.

It seems that the link doesn't work... however, at the MIDIbox16E page you will also find a reference to a 24P encoder from mouser/USA. But maybe it's cheaper to order the encoder from RS components in Germany, so that you don't have to pay additional taxes. Best Regards, Thorsten.

I could add an (software) option into the SysEx dump structure which disables the menu buttons and assigs them to MIDI controllers. Best Regards, Thorsten.

Hi, the amplitude modulators are used by the internal envelope generators of the SID. Unfortunately it isn't possible to control the amplitude levels directly - would be a nice extension for the LFOs :) The voice 3 off flag disconnects the third oscillator (which can optionally used as sync or ringmodulation master) from the output amplifier. It's usefull if you only want to hear the sound of the slave oscillators Best Regards, Thorsten.

Hi Dan, yes, you are right, for an endless scrubb wheel special routines have to be implemented. I could add it into the MB16E firmware, but since there are so much other things to do, I would prefer to wait for MIDIbox NG. It shouldn't be a problem to realize such a scrubb wheel extension with the upcoming plugin concept (-> assign 2 of 128 available digital inputs to a rotary encoder, send out MMC messages, print out the MMC on the display). Anothera advantage: on this way you only need one core module for a lot of pots/encoders/buttons/... List: sure, just post it. :) Best Regards, Thorsten.

Hi Frank, great that it's working - so I can freeze the routines and continue with the next features (Touch Detection for each fader, etc.) 74HC595: normaly it should deliver enough current for 8 LEDs, I don't notice problems with the intensity. However, there are some alternative 74xx595 available, which may be better - I don't have a oversight right here, but I know that there are some informations about the logic families at the TI (Texas Instruments) and Philips homepages. Best Regards, Thorsten.

yes, it works in this manner :) Best Regards, Thorsten.