-
Posts
15,246 -
Joined
Content Type
Profiles
Forums
Blogs
Gallery
Everything posted by TK.
-
Oh god, so much feedback for a work of three hours :o :D Christoffer: it seems that your MIDI interface isn't multi client capable - so the best solution: just use "Hubis feedback cable" (freeware -> web) which allows you to create virtual connections between multiple MIDI devices. I used this really usefull tool many years before I bought a newer MIDI interface - hopefully it still works with newer Windows versions... After the tool has been installed, you've 4 additional MIDI IN/OUTs. First you should remove the hardware MIDI device in your \windows\win.ini file; [logic] section. Logic should only use the virtual OUT ports. The JSynth editor should use another virtual OUT port. Now you can create virtual connections between the two virtual OUT ports and your physical OUT port with two "feedback cable" instances. It's a little bit tricky, but it works! :) And if it doesn't: "MIDI Yoke" in conjunction with MIDI-Ox should do the same Ian: oh, you are right. It's a good idea to add some simple button functions. Which could be usefull... I think one button for "dec", another for "inc", a button for storing patches and two others which allow to select the MIDI channel and the MIDI device number. Ok - I will support one DIN register with the next release. Maniac: let us know about the offer from the distributor in Poland! If the offer is good, we could maybe start a centralized order, because currently a lot of people are searching for encoders. Concerning the number of required encoders - since this is really a FAQ and I don't want to give imprecise answers to this issue anymore, I've started to design a frontpanel for my surface: So as you can see: 16 encoders are required. Btw.: not all parameters are controlled by encoders and buttons, some are only accessible with the button/jog wheel combination at the right corner. Btw2: all parameters will be accessible over the 4 buttons and the jog-wheel. So for people who don't want to create a big (and expensive) surface, this will be the low-cost solution. It's also be a nice solution for a low-cost 19" rack version :) Btw3: it's also possible just to left out some sections - not everybody wants this big modulation matrix Btw4: the purpose of the "assign" controllers is to assign them to internal or external (-> MIDI controller) functions. Btw5: SID 1/2/3/4 means that it is possible to control a lot of SIDs from this panel Btw6: the frontpanel design is preliminary Btw7: big thanks to NothernLight who gave me a lot of inspirations for this design! Best Regards, Thorsten.
-
Hi Roman, from my experience pseudo protocol structures like known from commercial controllers don't offer the flexibility like the simple Meta events concept. With the Plug-In capability (code can be downloaded via MIDI) updates of Meta events will be easier than ever before and therefore I will stay by this method. In other words: yes, will be supported - (really) any MIDI event strings will be programmable. Best Regards, Thorsten.
-
Patches can now be saved into a BankStick Program Change command switches between the 128 patches of a BankStick Beside of Mono and Poly also a Legato mode is available now Minimal support for a LCD - patch name, program number, MIDI channel and device number are displayed 50 example sound patches are available now new release of JSynthLib editor Firmware: http://www.ucapps.de/midibox_sid/midibox_sid_v1.4.zip JSynthLib: http://www.midibox.org/midibox_sid/jsynth_017_with_mbsid_rel4.zip Sounds: http://www.ucapps.de/midibox_sid/example_patches_v4.zip Have fun! :) Best Regards, Thorsten.
-
Ja, sieht soweit in Ordnung aus. Die Buttons kannst Du wie gesagt auch direkt an die freien Pins (mindestens 10) anschliessen. Tip zum Bestellen bei Reichelt: 10k und 220 Ohm Widerstaende am besten im 100ter Pack bestellen, dann gibt es Rabat. Ausserdem kann man gerade in der Digitaltechnik diese Widerstaende immer mal gebrauchen (z.B als Pull-Up oder Serienwiderstand) Taster: ich wuerde den Typ "DT_6" nehmen, den muesstest Du aber auf einer Lochrasterplatine aufloeten und diese dann intern ueber einen Winkel befestigen. Deshalb: am besten auch gleich 1-2 Lochrasterplatinen mitbestellen (H25PR200) Gruss, Thorsten.
-
Very mysterious, but alright :-/ Best Regards, Thorsten.
-
Yes, everything is perfect! The reason why there are different components on the new board is that I'm trying to unify all MIDIbox designs in order to avoid any confusion :-) Is it clear now how the 7805 has to be connected? I refered to the layout because it shows the pinning of the 7805: I (input side), _ (ground), O (output/+5V side) Important hint: use sockets! Solder all components to the board but don't put the PIC, 4051 and optocoupler into the socket so long as you ensured (with a multimeter or something else) that the voltage level behind the 7805 is +5V. If this is ensured, you can put the ICs into the sockets without danger Best Regards, Thorsten.
-
The output protocol of such encoders is mostly a gray code which ensures that the rotation direction can be determined with an higher count of pulses per revolution. So the only way is to decode this code with the PIC. A nice Plug-In for the MIDIbox NG ;-) Best Regards, Thorsten.
-
Servus - leider ist das erstmal nur die Leiterplatte, die restlichen Bauteile kaufst Du Dir am besten bei Reichelt. Wenn ich es richtig in Erinnerung habe, kosten sie nochmal zusaetzlich ca. 15 EUR, hinzu kommen dann noch die Potis und Taster (ca. 8 EUR). Der PIC muss dann auch noch programmiert werden, das koennte ich dann aber fuer Dich uebernehmen (kostenloser Programmierservice...) Wenn ich das neue Board erstmal getestet habe, wird es genauso wie bei der MBHP Fotos und eine Reichelt-Bestelliste geben, damit wird dann alles transparenter... Gruss, Thorsten.
-
Hi Dan, double sided boards are suboptimal, since a second layout mask for the upper side is absolutely required in order to prevent short circuits around the drill holes! So, either you should remove (etch) the whole copper plane of the upper side, or you could modify the top layers of the eagle files so that they replace the required bridges (but the effort is higher than just soldering the bridges) The MIDI chains are ok so long as your controller keyboard comes with an internal MIDI merger function (hopefully...), otherwise the MIDI data coming from the PC MIDI port will not be forwarded to the MIDIboxes - however, this is only required for SysEx configuration and for the case that you plan to use the soft-overtake feature. The SID should be directly connected to the Thru port of your MIDI controller keyboard for the lowest latency. The parameters can be controlled on this way: MB64 > PC MIDI IN > MIDI-OX Thru Function > PC MIDI Out > KB Thru > SID - on this way also the JSynth editor can be used in parallel A two-way connection to the SID isn't required unless you plan to read out the BankStick LEDs with higher voltages should be ok, possibly you have to reduce the value of the 220 Ohm series resistor on the DOUT module if the LEDs are not bright enough. Best Regards, Thorsten.
-
Yes - the NG design has one large DOUT and one DIN chain, each with up to 128 pins, and a definition table which allows to define the function of the pins. The chains will be served/updated every 500 uS so that they are (in addition to buttons/switches and LEDs) fast enough for encoders, LED rings, LED digits, etc. in mixed configurations - the reason why this flexibility is not provided by the 16F designs is the limited memory... Best Regards, Thorsten.
-
Ok, the basics are ok. I've read your posting again. Possible problem with the analog inputs: check the interconnections between the multiplexer inputs of the AIN module (J6) and J6 of the core module. Buttons: check the clock signals between core and DIN module (they are called "SC" and "RC"), because when the register chain is not clocked, only the exec button input is reachable for the core and triggers the functions of the other 63 inputs (no, the navigation isn't disabled). Best Regards, Thorsten.
-
Hallo Benjamin, Zu 1) ja, das Core Modul ist das Herz jeder MIDIbox, die restlichen Module sind Interfaces. Das LTC bietet keinen zusaetzlichen MIDI In/Out-Port so wie man es z.B von einer PC-Steckkarte erwarten wuerde, sondern bietet lediglich die Moeglichkeit, das Rx/Tx-Signal mit LEDs sichtbar zu machen, die Signale verstaerkt auf zusaetzliche MIDI-Buchsen zu geben und/oder die MIDI-Daten von einem RS232 Port zu beziehen. Das DIN-Modul ist der Standardweg um digitale Eingangssignale zu verarbeiten. Es gibt aber auch andere Moeglichkeiten, so koenntest Du beispielsweise die Taster aehnlich wie bei der MIDIbox Plus anschliessen (nach dem Multiplex-Verfahren). An welchen Pins Du die Tasten anschliesst, liegt an Dir, es waere z.B problemlos moeglich, die freien Analogen Pins (AN0-AN7) dafuer zu verwenden, per Multiplexing koennten so 16 Tasten abgefragt werden. Zu 2) Du moechtest die Daten nicht wirklich im RAM abspeichern, dort gehen sie naemlich nach dem Ausschalten verloren. Ich wuerde sie entweder im internen EEPROM abspeichern (hier stehen 256 bytes zur Verfuegung) oder im internen Flash (8192*14 bit, beim PIC18F452 16384*16 bit - der Flashspeicher kann "nur" ca. 100000 mal ueberschrieben werden, aber das sollte hier nicht weiter stoeren) ablegen. Oder gleich in einem externen EEPROM (also in einem "BankStick), was fuer Deine Anwendung die perfekte Loesung waere, weil Du auf diese Weise z.B fuer jede Performance einen eigenen Stick vorbereiten koenntest, und den Stick sogar extern gegen Ueberschreiben schuetzen koenntest, sodass die Daten nicht ungewollt geloescht werden. Btw. gleich noch ein weiterer Hinweis: nimm unbedingt einen PIC18F452. Ich habe fuer diesen Chip zwar noch keine Beispiele vorbereitet, aber er laesst sich wesentlich einfacher programmieren, weil der Speicher nicht mehr fragmentiert ist. Ausserdem kostet er nicht viel mehr als ein PIC16F877 (ca. 10 Euro). Und noch ein Geheimtip: bei Microchip kann man sich kostenlose Samples bestellen, die direkt ab Taiwan per Fedex-Versand verschickt werden und zwei Tage spaeter eintreffen. Auf diese Weise koenntest Du Dir auf die Schnelle 3 18F452 und 3 24LC256 beschaffen ;-) Zu 3) theoretisch ja, praktisch musst Du fuer speziellere Displays auch einen eigenen Treiber schreiben, moeglicherweise muesstest Du sogar fuer ein grosses LED-Display die gesamte Ansteuerung selbst uebernehmen (so wie beim MTC-Beispiel): das erfordert zusaetzlichen Hardware-Aufwand (DOUT Modul) Gruss, Thorsten.
-
Wie das Frontpanel des Unaussprechlichen (;-)) eindrucksvoll demonstiert, macht es wenig Sinn, ein Universalpanel zu veroeffentlichen. Das scheitert schon daran, dass nicht jeder die gleichen Taster, Potis, Fader, etc. verwendet (ist ja auch alles eine Kostenfrage...). Die Datei kann ich aber gerne weitergeben (war sowieso geplant), sie ist nun vorlaeufig unter http://www.ucapps.de/tmp/lc1.fpd zu finden. Falls sich spaeter herausstellt, dass irgendetwas nicht richtig passen sollte, wird es nochmal einen Update geben. Hilfslinien vermisse ich ebenfalls, deshalb arbeite ich meistens mit Zoll als Bezugsgroesse (-> gerade Werte) und rechne mir die Positionen schnell aus. Gruss, Thorsten.
-
Hi Mickey, no, the JDM cannot be enhanced by an USB port, because the required operation voltage is above 15V (USB supplies only 5V). Maybe other programmers with external voltage source can be updated more easily, but in fact it makes no sense: a ready-made USB module is very expensive (i.E USBMOD1 from FTDI for about US $27) and DIY'ing is too critical (USB chips are mostly SMD). So the most secure solution is just to buy the USB programmer from Don's site Best Regards, Thorsten.
-
Perfect! The PIC has been burned successfully and you get the default MIDI events. Only problem is that you forgot to tie all unused pot inputs to ground. When no 4051 chip is connected to a ANx input of the PIC, the appr. pin should also be connected to ground. All unused digital inputs have to be tied via a 10k pull-up resistor to +5V. Also the end of the DIN chain must have an pull-up resistor (see schematic) Best Regards, Thorsten.
-
Hi Dan, the replacements are ok. AA and FC versions will work - AA means a lower minimum voltage, FC is the high-frequency version. But in fact all EEPROMs will work No, Reichelt has no caps for pushbuttons. My recommendations: DT_6 (simply the best) TASTER_3301B (the cheapest, can also be used without knobs) DTL_2 (with integrated LEDs, but expensive) T_250A (vintage style) Some buttons are indicated with an additional code for the colour: bl (blue), ge (yellow), gr (grey), gn (green), rt (red), sw (black), ws (white) Best Regards, Thorsten.
-
Hi Jeff, yes, thats ok. The pin numbers can be seen in the new PCB preview: http://www.ucapps.de/tmp/mplus_new_pcb.gif (note that this board is a little bit different from the current schematic, but the power supply circuit is the same). Maybe you should use a small drill or a screw driver to enlarge the holes for the 7805. The crystal hasn't a certain direction, yes you can solder them directly to the pins Best Regards, Thorsten.
-
Hallo Al, wie ich gerade auch im News-Board geschrieben habe, wird es bald fuer ca. 7-8 Euro ein spezielles Board fuer die MIDIbox Plus geben. Damit laesst sich natuerlich auch eine "MIDIbox Plus 8" aufbauen, die nicht benoetigten Teile einfach weglassen... noch guenstiger (und kleiner) geht es nur noch, wenn man die Schaltung auf Lochraster aufbaut. Gruss, Thorsten.
-
Hi, normaly the checkboxes are updated automatically, since the flags are defined in the .hex file. However, just for double-checking: Oscillator HS Code Protection off WDT on PWRT on BODEN on LVP off CPD off WRT on DEBUGGER off Best Regards, Thorsten.
-
Nearly perfect - just two hints: the CNY17 should be replaced by a 6N138 circuit (see MBHP core module for the schematic) and the unused AN0-AN7 pins should be connected to ground Best Regards, Thorsten.
-
Hi Dave :) you are right, with your PCB (midibox_plus_pcb_dave_v2.zip) the hardware changes can be accomplished with less effort. Only an additional wire between pin RC4 and the R/W input of the LCD will be required in order to get the upcoming (probably "final") firmware release running. I will put all current PCBs into a special archive - in respect to the work of the creators and as additional "source of inspiration" for people who want to etch their own board. Btw.: I just have finished the new layout and will get the PCB in about 4 days in order to test it. It looks expensive, but it isn't: the estimated price is about 7-8 Euro for a premade 10cm x 8cm board and it's also nice for DIY etching since only a single layer is used (and 9 bridges...) Best Regards, Thorsten.
-
Thanks - I've already found somebody who helps :) Btw.: how about a worldwide net of MIDIbox PIC Programming service points in each country? ;-) Best Regards, Thorsten.
-
Yes, but you need to add the three other 10k pull-ups and the ground connections to the analog inputs in order to prevent random values. The "initial value indicator" is just a feature and no must. And the CNY17-II should be exchanged by a 6N138 optocoupler (circuit: see MBHP core module. The MIDIbox Plus schematics will be updated soon) Best Regards, Thorsten.
-
Due to sporadic problems with the MIDI-In port of MIDIbox Plus I've decided to change the hardware although it (mostly) works perfectly. A user sent me his board so that I was able to search for the root cause - I noticed that the CNY17-II optocoupler from his MIDIbox sends much weaker signals to the PIC than those from my circuit. It's exactly what I had expected based on descriptions from other users (they had to tweak the 220 or 1.8k resistor). It seems that the manufacturs of this optocoupler cannot guarantee the specified characteristics, especially because users who bought the IC from the same distributor like me (Reichelt) never reported a problem. -> the CNY17-II will be replaced by a 6N138 Since it's more difficult for me to change all the existing PCBs, I will create a new PCB with Eagle. This will allow you to modify the layout for your needs. I will also ask Mike for distributing premade PCBs of MIDIbox Plus in his shop, as I think that the design has still advantages compared to the MBHP; it's the low-cost solution. By this way I will also change the 74HC00 circuit (add a MIDI-In LED) and the interface to the LCD (additional read line improves the speed). More about the new PCB maybe in 2 weeks Best Regards, Thorsten.
-
Meiner Meinung nach ist Tor Arnes Design schoen ziemlich gut durchdacht. Zum Mischen eignen sich die Fader/Poti/Taster-Kombinationen besonders, weil sie raeumlich so zueinander zugeordnet sind, dass man die Kanalzuege ohne Beschriftung wiederfindet. Und zur Ansteuerung von Synth/Fx PlugIns/Software ist man mit der Pot-Matrix besser bedient, auf die man schnell und einfach alle Parameter legt, die in Echtzeit angesteuert werden sollen. Hierbei macht man allerdings Abstriche in Punkto Uebersichtlichkeit, deshalb sind Controller-Fetischisten bereits dazu uebergegangen, jeweils einen eigenen Controller fuer ihre Lieblings-Anwendungen zu basteln (siehe MIDIbox-Gallery) ;-) Man sollte uebrigens nicht an Tastern sparen, sie vereinfachen die Interaktion mit der MIDI-Software mehr als man zunaechst annehmen mag. Bei Logic Audio habe ich mir die wichtigsten Funktionen auf die MIDI-Tasten gelegt, weil ich sie so wesentlich schneller erreiche als ueber die Computer-Tastatur (vor allem, wenn sich mal ein anderes Fenster im Vordergrund befindet, und man mal schnell die Transport/Aufnahme-Funktionen ansteuern moechte...). Auch ein Traktor-Controller besteht hauptsaechlich aus Tasten (siehe Design von Andreas). Ich persoenlich werde wohl in Zukunft hauptsaechlich mit der MIDIbox LC herumspielen (http://www.ucapps.de/midibox_lc/mblc_surface1.gif - das Panel sollte uebernaechste Woche bei mir eintreffen), die MIDIbox64 nur noch als Sequenzer, und die restlichen MIDIboxen nach Bedarf fuer Plugins und Reaktor verwenden. Gruss, Thorsten.