TK.

Works at my side. Did you restart your MBSEQ after changes on the MBSEQ_HW.V4 file? Alternatively just type the "reset" in the MIOS Terminal Best Regards, Thorsten.

No, the configuration mechanism hasn't been implemented yet. The solution will be simple to use and even won't require a SysEx editor. Just store/edit the configuration file(s) on a SD Card -> done :) Best Regards, Thorsten.

Hi, Wilba's Frontpanel has 4 DOUT shift registers. You have to connect the DOUTX4 module(s) to J2 of the frontpanel, so that they are chained with the DOUTs of the frontpanel. Now these DOUT Shift Registers are available as SR number 5, 6, 7, 8, etc... Accordingly, you have to define following numbers in your MBSEQ_HW.V4 file: DOUT_GATE_SR1 5 DOUT_GATE_SR2 6 DOUT_GATE_SR3 7 DOUT_GATE_SR4 8 DOUT_GATE_SR5 9 DOUT_GATE_SR6 10 DOUT_GATE_SR7 11 DOUT_GATE_SR8 12 Go into the CV Configuration page and select the interface with the rightmost encoder: See also http://www.ucapps.de/midibox_seq_manual_m.html Best Regards, Thorsten.

There is a nice debugging option in MBSEQ: if a certain DIN (SR/Pin) isn't assigned to any function, the sequencer will output the appr. SR and Pin number of the button in the MIOS Studio Terminal. So, just disable all button and encoder pin assignments in your MBSEQ_HW.V4 file (e.g. by adding a # before the definition). Thereafter reboot your MBSEQ and press the buttons... the MIOS Studio Terminal should give you the right numbers which then have to be entered into the MBSEQ_HW.V4 file This feature also allows you to troubleshoot your soldering work: if a button triggers multiple messages, you know that there is a soldering error between the button and DIN register. Best Regards, Thorsten.

Hi, MBCV is written in assembly code, while analog toolbox is written in C. It's very very difficult to merge these applications, and I'm not planning to do this as the 8bit platform is expired anyhow. It's much more comfortable to implement this with the MIOS32 platform. As you can read in this posting MBCV V2 is planned: It would be possible to add the C++ modulation components of MBSID V3 like LFOs and ENVs as an option: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v3%2Fcore%2Fcomponents%2F Best Regards, Thorsten.

Please stop this debate now. Give Peter (Lindener) a bit more time to learn how this community is working. And Peter: please create and show the results instead of talking too much about visions which might never come true. Thats the best way to demonstrate that you are not only a "chatterbox" (german: "Dampfplauderer") Best Regards, Thorsten.

Both versions can be used. I/P works in the temperature range -40C to +85C, E/P in the range -40C to +125C - thats the only (irrelevant) difference. Best Regards, Thorsten.

Hallo, Du schreibst, dass Balken angezeigt werden - aendern sich deren Kontrast wenn Du am entspr. Poti drehst? Dann wurde das Display sehr wahrscheinlich nicht initialisiert. Grundsaetzliche Frage: - verwendest Du einen PIC18F4685? - hast Du bereits die richtige MIOS version aufgeladen? (-> mios_v1_9g/pic18f4685/midi/mios_v1_9g_pic18f4685.hex) Gruss, Thorsten.

Of course, once the final layout has been successfully tested. Note that the layout has been made with Altium instead of Eagle (Sebastian's choice...). Best Regards, Thorsten.

Only PCB and MagJack Yes, because it doesn't exist. There is an ASCII list and a link to Reichelt mainpage, because nobody created a part list at Reichelt yet... Best Regards, Thorsten.

This is a european bulk order! :) Shipping costs: - 2.00 EUR inside Germany - 4.00 EUR to other european countries - 6.00 EUR to countries outside europe Best Regards, Thorsten.

Du kannst im Clock Divider Menue die Timebase aendern. Mit 8 spielt der Track fuer 4 Takte, mit 4 fuer 8 Takte, mit 2 fuer 16 Takte, usw. Gruss, Thorsten.

es ist J16.RC1 gemeint Wenn Du das Core Modul nicht ueber einen USB Hub mit eigener Stromversorgung betreibst: ja - dann kann es bei sovielen Bauelementen auch irgendwann mal herumspinnen, weil die Spannung nicht reicht. Du gehst die Sache IMHO falsch an. Anstatt langsam die einzelnen Komponenten auszuprobieren, versuchst Du alles aufeinmal. So wird das nie etwas! Fange doch erstmal mit NUR 8 potis nach tutorial/011_ain an, danach 64 Potis nach tutorial/012_ain_muxed, danach 96 Potis, danach 128... schrittweise. Spaeter dann mal die Buttons und Encoder ausprobieren, auch dafuer gibt es entspr. Tutorials. Wenn Du hier erstmal gesicherte Verhaeltnisse hast, kannst Du auch mal die LED Ringe ausprobieren. Bevor das nicht der Fall ist, wirst Du die verschiedenen Effekte sehr wahrscheinlich falsch deuten. Gruss, Thorsten.

I'm planning a PCB batch order for the new MBHP_CORE_LPC17 module: Project page: http://www.ucapps.de/mbhp_core_lpc17.html The first prototype is working perfectly, so that the PCB layout can be used without changes. Only some labels have to be overworked to improve the overall impression. :) Due to the superior specs it will replace the MBHP_CORE_STM32 completely. SmashTV is planning to sell the remaining "Core32" boards to MBSEQ V4 users, since the STM32 performance is sufficient for this project (I will still use the STM32 for my own MBSEQ V4 as well). To future MBSEQ V4 users: please support him to sell the last boards, otherwise the big help that he gave us to provide MBHP_CORE_STM32 as a DIY friendly solution will result into a financial loss! We count on your help! For users who don't plan to build a MBSEQ V4, the new MBHP_CORE_LPC17 module is the first choice of course! :) This module finally gives us a solution which doesn't require SMD soldering anymore. Instead we use a prebuilt LPCXPRESSO LPC1769 and mount it on the PCB which only contains easy to solder DIP components. Accordingly I see this as a perfect solution for the MIDIbox projects, as users don't rely on PCBs and/or SMD presoldering anymore. The MBHP_CORE_LPC17 circuit can even be built on a veroboard, or alternative PCB layouts could be created for special purposes (e.g. with reduced but sufficient feature set, or with integrated control surface components, etc..) However, for those who are interested on the complete PCB: just join this order! :) The estimated costs are 12.50 EUR 6.50 EUR due to the high quantity on this bulk order - thanks to everybody who attended! :) In addition a LPCXPRESSO LPC1769 is required which is available for ca. 30 EUR at Embedded Artists in Sweden, or 24 EUR at Watterot in Germany. There are resellers in other countries as well (e.g. Mouser: US $34) Costs for additional components: ca. 14 EUR Except for the MagJack (Ethernet) these components are typically available in local shops, but also (and especially) at Reichelt See also http://www.ucapps.de/mbhp/mbhp_core_lpc17_orderlist.txt (the MagJack is available at www.csd-electronics.de) So, the costs of a complete MBHP_CORE_LPC17 module is ca. 44 EUR (for germans who order remaining parts at Watterot and Reichelt) This batch order will only include a PCB + an optional MagJack, since it's a special part! When will it happen: in ca. 1..2 weeks, depending on the amount of requested boards. SmashTV is planning to provide complete kits later. Especially for europeans there will be additional batch orders for PCBs and MagJack handled by myself in future if enough people are interested. Future projects which will use the MBHP_CORE_LPC17 module: MIDIbox SEQ V4 has been ported to LPC17 and works stable. Due to the reasons described above, I ask future users to buy the remaining MBHP_CORE_STM32 modules from SmashTV first. Keep it fair! :) Only if you want to use the Ethernet option, a MBHP_CORE_LPC17 is the better choice. new synths will grow up. First experiments done by Nils (nI2S synth) and myself (speech synth) showing awesome results. MBSID V3 has been started as well (but won't be released before Q1 of next year) A simple but helpful USB MIDI / 2xMIDI IO / OSC bridge, e.g. to access a common MIDI synth from an iPhone/iPad application which sends or receives OSC messages without the usage of a PC. On-board IOs will be controllable via MIDI and OSC as well, e.g. if you want to control your coffee machine from an iPhone ;) MIDIO128 V3 is some kind of "low hanging fruit" and could be released very quickly. New features are for example: USB MIDI, two MIDI IOs, OSC receive and transmit, and a MIDI file player and recorder, e.g. to MIDIfy an organ and to start playbacks without the need for a PC MIDIbox CV V2 is a "low hanging fruit" as well. It will support all features of MBCV V1 + more CV channels (your choice how many are required), more triggers, gates and/or clocks (up to 128 with configurable characteristic and dividers), USB MIDI for best performance, 2 common MIDI IO ports, OSC MIDIbox NG V2: basically a superset of MIDIbox64, MIDIbox64E, MIDIbox MF, MIDIbox LC and MIDIO128 USB MIDI, 2xMIDI IO, OSC Configuration via text files stored on SD Card. Inclusive Sending and Receive NRPN and SysEx messages without programming And last but not least: since MIOS32 provides an open programming platform which supports C and C++ with already available low level drivers which abstract the hardware, it should be *much* easier for programmers to develop their own applications and share them to the community than with the limited (and ca. 10 years old) MBHP_CORE_PIC module. :) See also http://www.ucapps.de/mios32_c.html We are not speaking about the future, the future is now! ;) Finally the link to the Wiki page where you can add your name if you are interested: http://www.midibox.org/dokuwiki/doku.php?id=tk_mbhp_core_lpc17_bulk_order Shipping costs: - 2.00 EUR inside germany - 4.00 EUR outside germany Best Regards, Thorsten.

Wow, you are already very fast with your fingers! :) Best Regards, Thorsten.

Hi Sam, could it be that you tried to upload midimerger_pic18f_without_bootloader.hex? This .hex file is intended for people who want to flash the PIC directly without the usage of a bootloader. The midimerger_pic18f_with_bootloader.hex starts at 0x400 and can be uploaded with the MIOS bootloader. No, it isn't required to locate the code at 0x3000, as the merger is a standalone application which doesn't use MIOS itself (it only supports the bootloader - optionally) The midimerger_pic18f_with_bootloader.hex variant is selected in midimerger_v1_5/18f/reset.inc with MIOS_BSL_FLAG I'm surprised that the bootloader has been overwritten, as it protects the 0x000..0x3ff range. Do you still get an upload request after power-on? Best Regards, Thorsten.

Current status :) The control surface allows me to test parameter changes quickly w/o the usage of a CC panel in Logic (resp. a mouse) - good results are found much faster. Phonemes and patches can be stored on SD Card now. Note that this synth is still in experimental stage. Once I started to hack the speech engine (I already added bugfixes), the CS (more knobs for realtime editing!) but also the audible results (playing the formant synth directly!) could be much different ;) Best Regards, Thorsten.

Hi, it seems that the .hex format isn't compatible with MIOS Studio 2 anymore. Could you please try it with MIOS Studio V1? -> http://miosstudio.midibox.org/ (download MIOSStudio_beta9_4.zip) Best Regards, Thorsten.

Yes, thank you! :) I'm getting old! :santa: -> http://www.emu.com/support/files/download3.asp?Centric=1006&Platform=1&File=550 Best Regards, Thorsten.

Hi Yogi, the "options menu" has vanished, as MIOS Studio 2 only offers options which lead to a straightforward workflow to avoid such accidents! :) To your USB MIDI problem: this seems to be related to XP only, it's a Microsoft driver issue which only appears on certain computers. Somebody found an alternative driver for XP some time ago, which was open for other USB MIDI compliant devices (such as MBHP_USB and MBHP_USB_PIC). I believe that it should also work with MBHP_CORE_STM32... but my problem: I can't find the appr. posting anymore! :-/ However, it could make sense to search in the web for different USB MIDI drivers especially provided for XP. It wasn't from Yamaha, nor from Roland... but from a known company... Best Regards, Thorsten.

Definitely the MIDIbox of the week - great work! I will post this in the Wiki after server move. Best Regards, Thorsten.

Hi Robin, I agree with Peter. If you are using a potentiometer with lower resistance (1k is the ideal value in your case), and connect it to the core via a shielded cable, it should work without jitter. Best Regards, Thorsten.

I could have linked you there if you would have told me that you are a Windows user. A linux or MacOS user would be confused, or would think that Windows is required to run the toolchain, which isn't true. Since MIDIbox is a long-term project, we've all time of the world to improve the docs ;) But thanks for the suggestions (of course) Best Regards, Thorsten.

I don't think that this is the right way. The MIDIbox community is specialized on MIDI/synth/controller topics, small and therefore flexible - and especially very friendly as long as people don't start to bother because of missing informations or delayed support which can't be omitted for such a sparetime project. Arduino goes a totally different way. It's a generic device made for newbies who want to explore microcontrollers by programming simple applications. It explicitly goes the commercial and education route (another reason why it's clever from the creators not to add too much complexity by themself), devices made with Arduino can be explicitly sold in commercial devices which is ok as well as the effort is mostly done by the programmer himself. MIDIbox in distance is a huge work of a small number of people, most work has been done by myself over the last 12 years. It is and should stay a hobby. Of course, people who started with Arduino are always welcome to try MIDIbox as well, but I'm not interested to actively advertise the MBHP as an alternative to Arduino, especially not as general purpose platform. If this is for interest, then please start an own platform and community, and support it by yourself. Some people did this by themself in the past (also for MIDI/Music related projects) with success - so it can work! Best Regards, Thorsten.

See http://www.ucapps.de/mios32_c.html Each tutorial contains a README which describes some details - step by step The complete code is available on our subversion server If you are missing details in the Wiki, help to improve it! MIOS32 is very modular, changes in my own sources are aligned with me, experimental changes can be done in separate directories or svn branches (if really required) It's possible at application level, especially if the C++ flow is used. I for myself don't plan to do this work due to other plans. Not required, as the compile flow is very fast, and sources are sometimes using hardcoded parameters selected via #ifdef/#if to simplify customizations. Creating libraries would lead to higher RAM consumption and too many variations - no real advantage. Best Regards, Thorsten.