TK.

Thank you! This mistake happened during code changes that I made to share parts of the MBSEQ firmware with future MIOS32 applications. MIDIboxSEQ V4.0beta44 ~~~~~~~~~~~~~~~~~~~~~ o session can be selected again [/code] Best Regards, Thorsten.

Hi, MIOS8: just generate (valid) MIDI events to output the variable value, e.g. MIOS_MIDI_TxBufferPut(0xc0); // program change allows to send one additional 7bit byte MIOS_MIDI_TxBufferPut(the_variable & 0x7f); [/code] or: [code] MIOS_MIDI_TxBufferPut(0xc0 | ((the_variable & 0x80) ? 1 : 0)); // program change + MSB of variable MIOS_MIDI_TxBufferPut(the_variable & 0x7f); Alternatively you could try the debug_msg module which is located under modules/debug_msg See also http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fmodules%2Fdebug_msg%2FREADME.txt It sends text strings to the MIOS terminal MIOS32 (to complete this posting): use MIOS32_MIDI_SendDebugMessage to generate debug messages with a printf like parameter list See also http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F003_debug_messages%2F Best Regards, Thorsten.

How about this variant? -> http://www.ucapps.de/mios/midibox_seq_v3_4g3.zip Best Regards, Thorsten.

No, I haven't increased the version number in the LCD message... strange, the code looks good now, even after the third review. Seems that I have to open my MBSEQ and exchange the core module to test it by myself :-/ Best Regards, Thorsten.

I reviewed the code and think (resp. hope) that I found the error: when checking the legato flag via AND the MIOS_HLP_GetBitORMask function has to be used to isolate the flag (the MIOS_HLP_GetBitANDMask function would isolate all other flags...) Please try http://www.ucapps.de/mios/midibox_seq_v3_4g2.zip Best Regards, Thorsten.

A comment to the OSC topic: I already tried this by tunneling the MIDI events (which are the most compact format) via MBSEQ V4 via Ethernet Router to a virtual BLM16x16+X running on my iPad and it worked - in both directions! The MIOS32 based BLM16x16+X could be easily adapted to support the OSC protocol as well, regardless if the compact MIDI based format (embedded into OSC packages), or a "human readable" format, or any other format expected by a DAW is used. This is on my TODO list. :) In mid term I want to separate the whole OSC parsing of the different proprietary formats from MBSEQ into a single source module which can be included into MIOS32 applications, so that enhancements are automatically inherited by all applications. The physical implementation is your topic ;) Best Regards, Thorsten.

Ooops! You are right! It's time to automate the release flow! Please download the .zip file again Best Regards, Thorsten.

perfect specs! But: Epuisé :-/ Best Regards, Thorsten.

Hi, it's always a surprise to read from people who are using a MIDIbox for so long time without the need for troubleshooting! :) I remember that somebody reported this issue a while ago, my statement was that it requires a notestack for proper handling, and that there isn't enough free RAM for such a feature (it has been solved in MBSEQ V4) But I just got an idea how to realize a minimalistic 2-level notestack which should be sufficient for this purpose. Could you please try following version: http://www.ucapps.de/mios/midibox_seq_v3_4g.zip I'm currently not able to test this (I would have to open my MIDIbox to exchange MBHP_CORE_STM32 by a MBHP_CORE). For the case that it doesn't work and you've assembly knowledge: this is the change in src/midi_evnt.inc ;; -------------------------------------------------------------------------- ;; FUNCTION: MIDI_EVNT_AOUT_GatePinSet ;; DESCRIPTION: Help Function which sets a Gate Pin independent from the interface ;; IN: ;; o pin number in WREG ;; o value in MIOS_PARAMETER1 ;; -------------------------------------------------------------------------- MIDI_EVNT_AOUT_GatePinSet SET_BSR GATES movf MIOS_PARAMETER1, F bz MIDI_EVNT_AOUT_PinSet0 MIDI_EVNT_AOUT_PinSet1 call MIOS_HLP_GetBitORMask #if 1 ;; extension for legato handling ;; if gate was already set, save this state in GATES_LEGATO movwf PRODL andwf GATES, W, BANKED iorwf GATES_LEGATO, F, BANKED movf PRODL, W #endif iorwf GATES, F, BANKED return MIDI_EVNT_AOUT_PinSet0 #if 1 ;; extension for legato handling ;; if GATE_LEGATO flag is set, clear this flag and exit ;; otherwise clear the flag in GATES (so that the pin is set to 0) movwf PRODL call MIOS_HLP_GetBitORMask andwf GATES_LEGATO, W, BANKED bnz MIDI_EVNT_AOUT_PinSet0_Legato MIDI_EVNT_AOUT_PinSet0_NoLegato movf PRODL, W call MIOS_HLP_GetBitANDMask andwf GATES, F, BANKED return MIDI_EVNT_AOUT_PinSet0_Legato movf PRODL, W call MIOS_HLP_GetBitANDMask andwf GATES_LEGATO, F, BANKED return #else call MIOS_HLP_GetBitANDMask andwf GATES, F, BANKED return #endif [/code] Best Regards, Thorsten.

The random function isn't documented in the manual, because it was initially planned as an easter egg ;) Best Regards, Thorsten.

This is a switching PSU with 5A for 5V supply (far too much), and 2.5 A for +12V (far too much as well) In addition, switching PSUs are not good for analog stuff. Unfortunately I can't give you an alternative proposal for the US (in germany we would order at "Pollin" where matching PSUs are mostly available for 5..10 EUR), but I can give you some specs: 1A for the 5V supply, only if a BLM16x16+X should be connected maybe 2A would be better. ca. 100 mA for the +/- 12V supply Best Regards, Thorsten.

thanks for reporting this! It always worked this (wrong) way, and it seems that nobody noticed this before. ;) Fixed - the change will be available with beta44 Best Regards, Thorsten.

Everybody in the list will get a PM in ca. 2 weeks (once I got the PCBs) Best Regards, Thorsten.

Beta43 is available now: IDIboxSEQ V4.0beta43 ~~~~~~~~~~~~~~~~~~~~~ o delayed mute/unmute which is synched to the measure. It can be enabled individually in the global options menu (UTILITY->OPT) o trigger assignment page: trigger layer of the current assignment automatically selected (alternative way to select a trigger layer) o random page: random values can now be generated for all parameter and trigger layers (resp. drums: parameter and drum instruments). The selection is scrollable with a GP encoder. o random page: special behaviour for drum tracks: parameter layers and each individual drum instrument can be randomized (no triggers in this mode to keep the code simple) o random page: new values will only be generated when "Generate" button is pressed, or for a single layer if the GP button under the appr. layer is pressed. [/code] Additional informations: This package contains two precompiled binaries: one for MBHP_CORE_STM32, another for the MBHP_CORE_LPC17 module Gridracer: the reported copy issue should be fixed Best Regards, Thorsten.

Implemented in beta43! :) Best Regards, Thorsten.

I implemented this, it will be available in the upcoming beta43 Best Regards, Thorsten.

Short updates: I've ordered the PCBs, the final price will be less than 10 EUR! I will start to collect money once I got the batch and know the costs exactly. Some people proposed to use sockets for the LPCXPRESSO module, I will add them as an option to the BOM (orderlist). The orderlist also doesn't list the SIL headers for the LPCXPRESSO module, which have to be added as well. Best Regards, Thorsten.

Hi Tristan, are your modifications based on the new MBHP_MF_V3 module, or on the old module? -> Many improvements have been made (ok, still no separate LM317 for each motor), also firmware wise, as the PIC doesn't use the MIOS_MF drivers anymore, but an overworked version which controls the motors faster (drawback: nothing else can run in parallel anymore) A L293D H bridge is used now, since it's cheaper and better than TC44xx The bridges are directly connected to the PIC for faster access. There is also support for remote calibration in MIOS Studio, each motorfader can be calibrated separately. Best Regards, Thorsten.

This is a good entry point: http://www.ucapps.de/mios32_c.html It makes sense to read the READMEs from the beginning, as they explain the basics step by step. There are various approaches for LED matrices, the BLM16x16+X is the most flexible one: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fblm_scalar%2F There are no drivers for high precision rotary encoders yet. The existing MIOS32_ENC driver only works for common rotary encoders with a scan speed of 1 mS Best Regards, Thorsten.

Unter http://www.ucapps.de/mios_download.html gibt es einen LCD Interconnection Test, mit dem sich jede einzelne Leitung von MIOS Studio aus ueberpruefen laesst (siehe README.txt) Koenntest Du den mal ausprobieren? Gruss, Thorsten.

Doesn't sound that bad, especially since you are experienced in supporting people, and since you are planning to create a new application which could be interesting for some people around here. Kits are always welcome as well. But I can't decide this yet, because you are unknown to the community. I would propose that you are starting to document the progress in this forum. When it goes into the right direction, you will get my official approval. Hope that these conditions are ok for you. Best Regards, Thorsten.

Once you selected the AOUT port and Channel #16, the outputs can be triggered with Note C-1, C#1, D-1, D#1, E-1, ... upwards Simple? Best Regards, Thorsten.

MBSEQ is simple XOR logic. My hope was, that the confusing and incomplete user manual + the change log (search for "AOUT", resp. type "help" in MIOS Terminal to find the "testaoutpin" command) makes this clear ;) Best Regards, Thorsten.

Yes, you are right, it has only two 74HC595, accordingly you should set: DOUT_GATE_SR1 3 DOUT_GATE_SR2 4 DOUT_GATE_SR3 5 DOUT_GATE_SR4 6 DOUT_GATE_SR5 7 DOUT_GATE_SR6 8 DOUT_GATE_SR7 9 DOUT_GATE_SR8 10 In addition, you have to set following values: # number of first and second DOUT shift register used for GP LEDs GP_DOUT_L_SR 3 GP_DOUT_R_SR 4 to: GP_DOUT_L_SR 0 GP_DOUT_R_SR 0 Probably this caused the problem. Best Regards, Thorsten.

The preset uses the wavetable sequencer to produce the gated sound. It just toggles the filter cutoff frequency between low and high values (-> see WT 3 track) This allows you to create nice rhythmic patterns. You could also use two WT tracks in parallel and run them at different speeds and track lengths to create euclid-like patterns. Best Regards, Thorsten.