TK.

Seems that the DIN is not working Link to the troubleshooting guide: http://www.midibox.org/dokuwiki/din_module Best Regards, Thorsten.

I think, it's a great idea to try it with a PIC24F, it's especially a nice learning project. And I must say, that I still prefer external merging and routing (in my case: with the MIDIbox Router) for the same reasons like you. Routing through a computer would add some additional latency and especially unwanted jitter. Best Regards, Thorsten.

Only difference between V2 and V3 is, that V3 supports a Start/Stop signal. What happens, if this signal is not connected (Pin RC1)? Best Regards, Thorsten.

It's still unclear to me, how your frontpanel(s) will look like, therefore it's hard to say, if two sets of groups buttons could really be useful for your design. Best Regards, Thorsten.

If ADCON1.PCFG is set to 0xd instead of 0x6 (see PIC18F4685 datasheet), this should work. But I don't know, how much additional noise will be added to the analog inputs - the pots could start to jitter. Best Regards, Thorsten.

No, MBHP_IIC_MIDI is no option, as this module is not supported by the firmware. It is possible to connect the USB IOs directly to the core module (Port J11), but for a synth this isn't recommented, as this will result into a ground loop between the Audio and USB lines. Instead, I would isolate the MIDI INs with optocouplers, and don't connect the grounds together - as usual Best Regards, Thorsten.

Ok - but this is just the lead engine! Left and right channel settings can be edited indidually, you only need to decide by yourself, how to partitionate the available LFOs and ENVs. Merge the two audio channels, and you are done. I assumed, that you are asking for something more advanced - and the answer is: explore the multi engine in conjunction with some clever ensemble settings ;) Best Regards, Thorsten. P.S.: for the case that this hint is hidden in the user manual too well enough: press SHIFT+Select button #1 in order to edit sound parameters of both channels, L or R only (3 options are available: LR, L-, -R)

As you already noticed, the old programming examples are obsolete. The usage of up to 8 pots (or 4 joysticks) is natively supported by the V2 CS; each pot can be assigned to two parameters with a definable min/max range. The information is stored in a patch, which means: for each patch you can optimize the parameter mapping and range for best live usage. Unfortunately, your exact usecase isn't natively supported. There isn't a button which allows you to switch between parameter sets (this would be difficult to realize with the current code, too many places which need to be changed), but maybe you like the already implemented solution much more? Parameter assignments can be easily changed in the Knobs menu. Best Regards, Thorsten.

This can be done with the Multi Engine. It gives you individual access to the 6 voices, and when you disable Poly mode and assign the voices to specific oscillators, you can create very complex layer sounds (more complex than with the lead engine, as each voice has it's own LFO/ENV). Or you can assign the voices to different keyboard zones/channels to create C64ish tunes... Best Regards, Thorsten.

Seppoman asked me for a SSM2044 demo, so here it is: -> http://www.ucapps.de/mp3/midibox_sid/mbsidv2_bassline_demo4.mp3 This is the first jam session I recorded with Logic8 - not everything is under my control yet (especially the distortions ;)) I especially love the part, where the SSM filter is routed through a guitar amp Fx. It starts at 1:39 :) Best Regards, Thorsten.

Yes, an USB hub will help The advantage of seperate IOs: higher bandwidth (as MIDI events can be sent out in parallel to multiple MIDI outs), and you don't need to merge the inputs, resp. chain the IOs Best Regards, Thorsten.

Yes, we have to solder the chip by ourself - but don't panic, it's a nice inexpensive project to get some practice, especially because TQFP32 has only 8 pins at each side Best Regards, Thorsten.

+ $400 to extend your AppleCare contract ;) Best Regards, Thorsten.

Hallo Gody, ja, mit einem zweiten MIDI Out Port geht das problemlos. :) Leider ist es nicht damit getan, die entspr. Buchse einfach parallel zur Ersten anzuschliessen. Man muss ihn Buffern, damit ihm (umgangssprachlich) nicht der Saft ausgeht. Deshalb gibt es das MBHP_LTC Modul: -> siehe http://www.ucapps.de/mbhp_ltc.html Wobei Du fuer Deinen Anwendungsfall auf den zweiten 74HC00 und den MAX232 verzichten kannst. Gruss, Thorsten.

Apparently I don't understand my own jokes anymore ;) Best Regards, Thorsten.

No, there are no group selection buttons at the frontpanel of my own MBSEQ - to which buttons are you refering exactly? (just give me the link to the .gif file) > Have i told you that this page is very impressive? It is! Thanks! :) Best Regards, Thorsten.

Interesting, this is a definition error in the encoder table, because the "OSC Release" encoder should be assigned to SR4, Pin 0 (and 1) Due to some magic 3,8 leads to the same assignment as 4,0 (ok, replace "magic" by "sr*8 + pin" ;-)) I changed the source code to: [tt] ENC_ENTRY 4, 0, MIOS_ENC_MODE_DETENTED2 ; Osc release/pulsewidth/assign #5 [/tt] Best Regards, Thorsten.

Optimized Windows Driver: it's bundled with the firmware and our vendor ID. We don't need to pay extra money for it. In other words: for us it's free! :) Schematic: more patience please! I've already access to the schematic, but it's confidential. I already got the permission to publish an own schematic, but I won't do this before I tested the current chip configuration. I will get the evaluation board in 1-2 days, and a schematic can be expected this weekend. Don't worry, it's a very simple circuit, I just don't want to break the rules! However, the cheapest solution is to re-use the Ploytec PCB, and to add the MIDI IOs externally (e.g. soldered on a veroboard) if required. The MIDI I/O sockets are not required if you connect the GM5 IOs directly to the MIDIbox Link port J11 of your core modules. If somebody prefers an individual solution, he will get all sources which are required to layout the board... soon! Best Regards, Thorsten.

Update: Ploytek will also provide PCBs for 2.50 EUR pp.! They are prepared for one MIDI In and one MIDI Out Socket, the remaining 4 IOs are available on junctions, and can be directly connected to MBHP_COREs, or alternatively to external MIDI IO sockets (+ optocouplers) Please add the desired PCB quantity to the third column Best Regards, Thorsten.

Yes, there is an advantage: inside configuration pages GP buttons/LEDs are used to control soft functions (parameters displayed on the LCDs). With "DEFAULT_SRM_BUTTONS_NO_UI 1" all BLM rows display the trigger layers, and you are able to change the triggers with the BLM buttons, whereas with "DEFAULT_SRM_BUTTONS_NO_UI 0" the upper BLM row is used as GP button/LED replacement, which means that you have to go back to the edit page in order to change the triggers of the upper track. In other words: with "DEFAULT_SRM_BUTTONS_NO_UI 0", you won't get direct access to track 1/5/9/13 inside configuration pages no No, these are different functions. Track buttons allow you to select one or more tracks inside a group, whereas the group buttons allow you to select track 1-4/5-8/9-12/13-16 So, with 2x4 = 8 buttons you control the selection of the 16 tracks Best Regards, Thorsten.

Could it be, that J2 isn't 1:1 compatible to MBHP_SID:J2 and MBHP_CORE:J10? (10 pins instead of 8 pins) Best Regards, Thorsten.

Hi Razmo! :) Please note, that the most current version (with corrections, etc...) can always be found here: http://svnmios.midibox.org/trunk/apps/synthesizers/midibox_sid_v2/doc/ Best Regards, Thorsten.

Addendum: you are allowed to re-enter the quantity of chips you are planning to buy to give over people the possibility to join the first batch order. Please only take care, that the n x 250 pieces criteria is fullfilled Best Regards, Thorsten.

Ok, after a phone call I got some very good news: 1) each GM5 chip provides 5 physical MIDI IO ports! (means: 0.70 EUR per IO port - compare this with commercial interfaces! :)) 2) an external EEPROM for storing the vendor ID won't be required - and we will get our own vendor/product ID (I will use one of the IDs which have been sponsored by voti.nl) 3) the windows driver will be multi-client capable No need for virtual cable/router workarounds MacOS is multi client capable w/o additional driver 4) They consider to sell PCBs More infos (especially about the prices) soon Best Regards, Thorsten.

SMD != SMD - there are differences between package formats and pin pitch... To give you an impression: this is the pitch which is good for DIY, and which can be expected for GM5: And this is the pin pitch of a FTDI chip: (sorry, but my camera had problems to zoom this properly ;)) Best Regards, Thorsten.