TK.

I don't like both of them. The serial protocol of the DAC7614 (especially the LOADDAC# line) will cost too much performance when many outputs should be updated periodically (MBFM, MBSID), and the LTC2620 comes only in a Lead Package, which means, it could happen, that they won't be available in 1-2 years anymore. A quad-DAC on a single board would be ok. Something similar to the DAC7614 (it can optionally be supplied with +/- 5 V, this is really great!), but with serial output and w/o the need for latching the DAC address would be perfect Best Regards, Thorsten.

Hi, as trigger outputs you can optionally use the 8 pins of J5 - this option has to be enabled within the setup_*.asm file Note that the AOUT_LC module is not supported by MBSEQ V2, it requires MBSEQ V3 (-> PIC18F4620, MBHP_IIC_MIDI module) Best Regards, Thorsten.

Hi Chris, it can have various reasons - either the MIDI In of your Core is not working, or the MIDI Out of your PC. It could be a software driver of your MIDI interface, swapped pins on the MIDI In plug, a bad soldering joint, etc... I've written down some tests which help you to debug this: http://www.ucapps.de/howto_debug_midi.html If they don't help, please write down the test IDs and the appr. results - maybe this could give somebody a hint about what is going on. Best Regards, Thorsten.

These a good points, Moebius! In general I'm not sure if the price/quality ratio of the MAX525 is still justifiable today (2 years have passed after the first release), and on the other hand I see users (including me) who just only want to control some CC's (like cutoff, resonance via MBSID or MBFM), where linearity doesn't really matter, and R-2R latters consume too much area if you want to realize more than 2 channels w/ high resolutions. But your point about parallel interfaced DACs should also be considered - are there better/cheaper ones available (I don't think so, but I could be wrong). Best Regards, Thorsten.

The reason why I gave you the link is, that the ML303 is a superior TB303 clone (although it's DIY, even professional musicans own it) which includes a sequencer which can alternatively send MIDI events. This means: you are able to build a 100% look-and-feel 303 sequencer + some additional features, which should be easily connectable to MBSID. The analog board can be omitted... and the digital part gets use of a PIC18F452, which shouldn't be new to you. I just feel that this is exactly for what you are searching for (so long the MBSID V2 breakout box is not available - I guess that this can still take one year) --- yes, the forum is in german, but there is an english section where you could ask for details. Sorry, I cannot give you much more infos, I never built this one, but I know the designer. Best Regards, Thorsten.

I'm not sure here, I never needed more than one MBFM - so, it's really your own decition. If you like the workflow, you could prepare the sounds from a "main" MBFM with frontpanel, and send the ready made patches via SysEx to the other MBFM, which consist of a MBHP_CORE, MBHP_OPL3 and BankStick module only. This can be done from the CFG menu (press the CFG+SyxD button) Best Regards, Thorsten.

Hi Robin, have you already considered to call the DIN_NotifyToggle(pin, pin_value) function, like MIOS would do when a button is pressed? Best Regards, Thorsten.

Yes, see also http://www.midibox.org/forum/index.php?topic=7766.msg53661#msg53661 (a thread you've started by yourself ;-)) Best Regards, Thorsten.

Hi Seppoman, from the feature list and from the availability (it's even available at Mouser) it looks very good! :) Only disadvantage I see is the high linearity error of +/-2LSB typical and +/-6LSB max (the MAX525 has +/- 0.5 LSB), which means +/- 3 mV, but I think that this is acceptable (or do I oversee something?) SMD is ok for such a module (total newbies should start with the R-2R latter, this gives them a training on handling the soldering iron ;-)) 8 trigger outputs (-> 74HC595) are a must Best Regards, Thorsten.

the other hand is mostly busy with tweaking the rotary encoders... ;) Shift buttons are a nice possibility to save money, but they mostly lead to compromisses Best Regards, Thorsten.

Could you please continue this discussion via PM? Thank you! I lock the thread for the case that you miss to read this "strong wish" Best Regards, Thorsten.

I'm not sure if I understand you correctly - do you mean, that it would be enough if the inbuilt 303 style sequencer of MBSID could be clocked via MIDI? This option is already avalable... Sync24 is not possible. Or do you refer to another part of this thread? Best Regards, Thorsten.

I'm not sure if I understand your question correctly. MIDIbox FM provides 4 independent instruments and a drum kit, they have dedicated MIDI channels which can be changed from the CS or from JSynthLib, and which can be stored in one of 32 ensembles. If you use 2 MBFM in parallel, just assign the instruments to different channels. For the drumkit, either use another channel as well, or map the drums to different keyboard zones. So, why do you need a core for reassigning the channels? Or did I oversee something? Best Regards, Thorsten.

Yes, I'm using MBHP_BURNER for this, the 4620 and 4550 were the reason why I built this programmer, because P18 was the only software at this time which was reliable enough. Best Regards, Thorsten.

No, otherwise I would have mentioned this option on my website. From the beginning I never planned a CS option which allows to control multiple synths, this was a basic design desision and cannot be undone w/o a major redesign (new chip, new application, new frontpanel) Best Regards, Thorsten.

For Inc/Dec buttons you need to set the "CS_MENU_USE_INCDEC_BUTTONS" switch to 1 For a 1x16 LED you need to change the display layout under cs_menu.inc, "CS_MENU_Handler_Init_MainPage" and "CS_MENU_Handler_MainPage" (sorry that the code is located at two different places, but this was to save performance) Best Regards, Thorsten.

Hi MIDIbox LC users, I found a stupid bug in the meter handling, which caused an indeterministic update of the LEDs. I never really noticed this with Logic, since the incoming meter values are sent in a way which overrides the effect. If you are using a different host software (e.g. Cubase or Nuendo), and noticed a "strange behaviour" (I've read about this several times), then don't hesitate to use the new version. It's available under http://www.ucapps.de/mios_download.html (midibox_lc_v1_6a.zip) Best Regards, Thorsten.

It's not that difficult, but if somebody builds up such an application from scratch, I would estimate a working effort of ca. 6 months - considered, that he knows about MIDI and embedded programming, but never implemented a sequencer before... If somebody thinks, he could do this in less time, than hands up! Best Regards, Thorsten.

Hi, in the meantime there are so many people with hardware design skills here in the forum, that I would like to ask if somebody is interested in creating a successor of the AOUT module which is not based on the expensive MAX525, and which is easier and faster to build than a AOUT_LC module. With design I mean to develop the circuit, to create the PCB layout and to write some documentation Only requirement: the used chip(s) should be easily available. Number of channels and gates + additional options (e.g. CV offset, etc.) to be discussed w/ the community I will take over the software part if required... Best Regards, Thorsten.

Hi Alex, 1x16 LCDs are not much cheaper than 2x16 LCDs, and the patch name has 16 characters - so I would consider a 2x16 LCD. You will see the MIDI channel as well, which is a useful information. The "datawheel" modifies the patch by default within the main screen, so that no software changes are required Best Regards, Thorsten.

Hallo, im Zweifelsfall kann jemand aus dem Forum (z.B ich) Dir die PICs flashen Gruss, Thorsten.

Hi Alex, the usage of another software to convert a note value to velocity just sounds "perverse" ;-) I think there are two problems: one in the configuration, another on your AOUT_LC board. Configuration: doublecheck the settings. Use the select button to check the other channels as well. If you are unsure, just upload the application again - you should get the default setup with linear curve. The calibration is only hardware specific (you adjust the pots), there are no related values which would be stored anywhere Hardware: check the output voltage of the R-2R latter - does it behave linear? If yes, the error might be around the OP, if not, maybe a resistor of the R-2R latter has no contact? Today I tested the calibration with a MBHP_AOUT_LC module, it works. Best Regards, Thorsten.

Hi John, it's an older application which was published at a time where the DETENTED2 mode was not implemented. Just copy a mios.h file from a newer application (or from the migration/ path of the MIOS package) into the MIDIbox TC folder, thereafter it should work Best Regards, Thorsten.

This topic has been moved to Miscellaneous. [iurl]http://www.midibox.org/forum/index.php?topic=7827.0[/iurl]

Hi Alex, so far I remember, I only tested the calibration mode with a AOUT, but never with a AOUT_LC module... it could be a bug, but I'm not sure (because the implementation is straightforward) When the CV output is assigned to a CC (e.g. modulation wheel), do you see a linear change with increasing CC values?? If not, it's a hardware problem Best Regards, Thorsten.