TK.

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.

it's realized in a way like I would implement it with hardware (I had some flip flops in mind ;-) Did you also notice the credits in seq_scale.inc? :) Best Regards, Thorsten. q

Hi, yes, each OPL3 chip requires a dedicated core - the application is already extremely busy (more busy than the MBSID) due to all the software engine features, no chance to control an additional OPL3 Best Regards, Thorsten.

Hi Chris, it seems, that a track between the 7805 and pin 31/32 is broken, this might affect port J10 as well, accordingly the supply of the SID module You can follow the tracks with the probes of your measuring instrument in order to find the location, where the track is broken or "interrupted". It could also be a bad soldering joint, but this is hard to say w/o knowing, which board version you are using Best Regards, Thorsten.

How about MIOS_ENC_MODE_DETENTED2? See also http://www.midibox.org/dokuwiki/doku.php?id=encoder_types Best Regards, Thorsten.

Yes, all 7 buttons of CS Step B don't have an appr. menu entry Best Regards, Thorsten.

Since in the meantime so many people request to join the alpha testing phase, I'm now distributing the current snapshot under ucapps.de/tmp. The current build is located under: expired I will only add a short notification to this article whenever I update the package, changes are documented in the CHANGELOG.txt file Best Regards, Thorsten. Edit: this thread is expired, MIDIbox SEQ V3.0 has been officially released under http://www.ucapps.de/mios_download.html

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