TK.

The normal way to reset the sequencer and to play from step 1 would be to send a MIDI Clock Start event (FA) Advantage: this will synchronize the MBSEQ also to your other devices. If you want to manually reset all tracks to step 1, just press the stop button two times - there is no need to do this via CC Best Regards, Thorsten.

Hi Dan, before deciding in which direction we can help you, please check if the core is running. Open MIOS Studio, connect to the core and enter "help" in the MIOS terminal -> do you get some messages? Thereafter enter "play" -> does the sequencer start to play? Best Regards, Thorsten.

I guess that you've to skip the initialisation of these pins in BLM_CHEAPO_Init: // initialize all pins of J5A and J5B as outputs in Push-Pull Mode for(pin=0; pin<8; ++pin) MIOS32_BOARD_J5_PinInit(pin, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); [/code] changed to: [code] // initialize all pins of J5A and J5B as outputs in Push-Pull Mode for(pin=0; pin<6; ++pin) MIOS32_BOARD_J5_PinInit(pin, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); No modification is required when calling MIOS32_BOARD_J5_Set in this case, since A6/A7 are configured for alternate mode (and not GPIO mode), and therefore won't be overwritten. Best Regards, Thorsten.

Shipped today: jojjelito lindeborg rvlt ADK ranger930 DrKorg Ermangaver Antix Borba Will be shipped once I got the money: Fos romsom digga There are currently ca. 60 GM5 and 30 Mini-PCBs left Best Regards, Thorsten.

Thank you very much for the input! :) I updated the schematic: http://www.ucapps.de/midibox_kb/midibox_kb_fatar_df_76_interconnections.pdf And I changed the specification for the recommended parameters at http://www.ucapps.de/midibox_kb.html Could you please check if following changes are working ok at your side: set kb 1 rows 12 set kb 1 optimized on [/code] Best Regards, Thorsten.

Could you please enter "kb 1" in MIOS terminal, and copy&paste the output to this thread? MK9/BK9: I would expect this only for the 88 key type... however, this schematic shows the required connections: http://www.ucapps.de/midibox_kb/midibox_kb_fatar_df_88_interconnections.pdf Best Regards, Thorsten.

Yes, I only added the include files to make the eclipse project independent from the selected $MIOS32_FAMILY This shouldn't prevent you from adding private enhancements of course... The declaration has been added with r1302 more than 1 year ago. See also: http://svnmios.midibox.org/comp.php?repname=svn.mios32&compare%5B%5D=%2Ftrunk%2Finclude%2Fmios32%2Fmios32_dout.h%401302&compare%5B%5D=%2Ftrunk%2Finclude%2Fmios32%2Fmios32_dout.h%40144 In order to check differences between file revisions by yourself, just select the file: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Finclude%2Fmios32%2Fmios32_dout.h and thereafter select the "view log" function to display all changes. Best Regards, Thorsten.

Hi, which note_offset did you specify? The first note can be adjusted with this parameter. Best Regards, Thorsten.

yes, it's declared in mios32_dout.h, and therefore also included by blm_cheapo since the header file is part of mios.h Is this issue solved meanwhile? Because I've no explanation why it should fail - considered that I always compiled the firmware for a MBHP_CORE_LPC17 module by myself. Great to read that the Korg driver is working at your side! :) Best Regards, Thorsten.

First of all the LFO will always be quantized to the MIDI clock. We can see it as a feature, since MBSEQ is a sequencer and not a synth (or synth control engine) like MBCV V2 It will change it's value with each step - and this is the effect that you noticed. I'm not planning to integrate a continuous LFO into the firmware, as this would overload the CPU too much (I guess that everybody prefers a responsive sequencer...) But there are options which you could try out, maybe they already satisfy your needs. :) a) increase the speed of the track by setting the clock divider to 1 in the "Track ClockDivider" page b) or configure the AOUT port for CC output (see documentation: MIDI channel 9..16) And use the "Extra CC" (right side of the LFO page) at 384 PPQN - the CC number doesn't matter, but it should be >= 1 c) change to the CV configuration page, and increase the Slew Rate -> this will add an envelope to smooth the waveforms Best Regards, Thorsten.

Each instrument has it's own wavetable (which is nothing else than a sequencer which is either synchronized to the MIDI tempo, or which is freerunning). You can access (resp. edit) it in the WT page. Note that the wavetable is stored in the patch. Which means: instruments which play the same patch will also play the same wavetable! Best Regards, Thorsten.

I got following question from Alex: Considering the analog synths that I used in the last years, I would say that the bipolar option (+/- 5V) is the better, because most flexible choice. Best Regards, Thorsten.

It should work as long as you ensure that the grounds are connected together, and that the MIDI device doesn't output more than 5V at the Tx pin (which seems to be the case due to the USB powered approach) Ground is normally not available at the MIDI IN socket to avoid ground loops (bad for audio devices). But for this direct TTL connection you will need it. Best Regards, Thorsten.

Hi, Both - the planned MIDIbox NG, which should cover everybody needs, still hasn't been started. And than longer I'm waiting, than more contradicting requests I'm getting for this "general purpose MIDI controller". ;-) Anyhow, the tutorials guide you how to program such a controller directly, such a fully customized app will always fulfill your requirements better than any general purpose app could do. Best Regards, Thorsten.

MIOS Studio 2.3.1 is available now Updates: SysEx Librarian supports Virus B & C PIC .hex loader supports old (non MIOS based) projects improved robustness of PIC firmware upload when application crashed (or a non-MIOS based firmware is running) Best Regards, Thorsten.

STM32 compiles fine at my side, though it won't work since J10 isn't available for the Cheapo-BLM. I also don't see the problem with mios32_dout_reverse_tab, or the linker error. Are you sure that you are working with the original files in the repository? And it's essential to execute "make clean" after environment variables have been changed! Best Regards, Thorsten.

Shipped today: Rosch funkyboard schrabikus technobreath Altitude min struct gslug tosol Gilesjuk Triffki Ripper thebot Lanu64x MaG2k PeterK shimoda Q-p mburch Fresh Pants MicMicMan V`cent kvitekp tb323 Arkay Norbim1 Moduku sineSurfer artyman shaduz v4 Will be shipped once I got the money: jojjelito rvlt ADK digga ranger930 Ermangaver Antix Best Regards, Thorsten.

there are no changes - never change a running system! ;-) Ok, after one day 160 GM5 chips, 62 Mini-PCBs and all white GM5x5x5 boards are sold so far. 42 GM5x5x5 Boards are on Nils' request list. Already paid chips/PCBs will be sent out tomorrow morning - deadline is 8 AM CET Next shipping day will be mid of next week. Best Regards, Thorsten.

PMs are sent out! :) Unfortunately some names in the Wiki don't match with the forum user names, therefore I'm unable to contact them: Skwosh Fizzen Ckoester DaveyM69 Stobiepole ghost_danser Midisizer DrKorg Vasculator [/code] If you know one of these guys, resp. if you [b]are[/b] one of these guys, please send me a PM! Best Regards, Thorsten.

Short notice: I got the 250 GM5 chips + 100 MiniPCBs today. PMs will be sent out in ca. 1..2 days (I need some time to prepare this). Best Regards, Thorsten.

This could be related to an unstable connection (e.g. cable too long?) between MBHP_CORE_LPC17 and MBHP_AOUT_NG module Best Regards, Thorsten

Hi, to 1) there is no existing MIDIbox firmware which would allow to configure your requested setup. But: the basics are available - see http://www.ucapps.de/mios32_c.html for further details. Just take the code snippets and build the app by yourself :) to 2) similar answer. There is even a tutorial for DOG based touchplanel GLCDs to 3) a simple DOUT matrix will do the job... you should start with this once you got more experiences with 1 and 2 USB MIDI is natively supported, use MIOS Studio to upload the core via MIDI (regardless if USB MIDI or "common" MIDI) Best Regards, Thorsten.

Ja, Du koenntest eine LPC17 basierte MIDIO128 mit der MBHP_MF_NG und der PIC basierten MIDIbox64E kombinieren. Die MIDIO128 app hat einen integrierten MIDI router, so dass Du die MIDI Streams der beiden PICs zum USB Port weiterleiten kannst (und umgekehrt: USB zu den PICs). Gruss, Thorsten.

The MIDIO128 application is implemented in assembler - without knowledge of the PIC instruction set it will be difficult to add encoder functions. Instead I would propose to create a new application based on the template (apps/templates/sdcc_skeleton) Here are the programming examples for the functions that you need: http://www.ucapps.de/mios8_c.html Best Regards, Thorsten.

You could store the .html pages on your harddisk, then just click on the midibox_sid_manual.html file to enter the manual. Many webbrowsers will store the images as well (if the function isn't called "save as..." search for "archive" or "export") AFAIK nobody has created a cheat sheet yet Best Regards, Thorsten.