TK.

Somebody (I guess it was Wilba) requested to add these parameters for information purposes. They've no influence on the sound engine. Best Regards, Thorsten.

We need a term which can be easily shortened to a meaningful 3 or 4 character acronym. Therefore "Jam" is probably the best choice :smile: Patterns: my intention was to store them in the /SESSIONS/<name>/MBSEQ_C.V4 file (contains various local configuration parameters) Naming and separate files are too much overhead (this would especially affect the load time of a session for not so much value behind this approach). Format will be something like: # Num Gates Accent LivePattern 1 *............... ................ LivePattern 2 *.......*....... ................ LivePattern 3 *.......*....... *............... This way you can share patterns in postings on a textual basis, and users can just integrate (and re-arrange) them into a session with the text editor of the MIOS Filebrowser Best Regards, Thorsten. P.S.: I will be on vacation the next days, and come back to this topic in ca. 2 weeks

So, neither DIN nor DOUT is working - could the problem be located at the core module? Best Regards, Thorsten.

You are right. The term "performance" could be miss-leading for the page, here I see more the role of the mute, pattern and/or song page. Other proposals? In this new version the pattern selection has been separated for drum and common tracks (I guess that this is what you mean): -> http://www.ucapps.de/mios32/midibox_seq_v4_088_pre14.zip Are 16 patterns sufficient? At least it seems that LPC17 can still handle this, but RAM is almost completely allocated now and I hope that there are no stack overrun issues. Anybody with a LPC17 core ready for testing the integrity? (if all sequencer functions are still working?) Best Regards, Thorsten.

I found the AINSER64 resolution bug and fixed it in this version: http://www.ucapps.de/mios32/midibox_ng_v1_033_pre6.zip Here a usage example: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fainserhq.ngc Best Regards, Thorsten.

Ok, understood - needs more discussion the other day ;-) I couldn't resist to consolidate the Record, Live and Repeat page for a more ergonomic usage of the new functions. This should also solve the channel confusion and different recording usecases: -> http://www.ucapps.de/mios32/midibox_seq_v4_088_pre13.zip What is new: the Live and Repeat page have been removed. Instead we've now some subpages in the recording page for the different use cases: Left side: Track selection, Record on/off and Forwarding (previously called "Live") on/off The "Step Record" configuration is selected and showed at the right side (starting with Mode) Whenever this subpage is activated, step recording takes place. If any other subpage is selected, live recording is used instead. (e.g. step recording doesn't make sense together with the Pattern function - one possible confusion solved ;-) The live page enables live recording, and allows to select Mono/Poly, Auto-start and quantisation. The new pattern page used for pattern based recording (and playing) If a drum track is selected, individual patterns can be assigned to the Drum instrument selected with GP9 (or played from the keyboard). If a common track is selected, GP9 allows to switch between Mono/Poly mode instead. Copy/Paste are possible with GP15 and GP16, but also with the dedicated buttons if this subpage is selected. The MIDI configuration page is similar to the page that we know from MENU->MIDI We've 4 busses, each bus can either be assigned to control the T&A function (Transpose and arpeggiator), or the Recording function (which is used for MIDI forwarding as well - previously called "Play Live") The dedicated Recording Port/Channel has been removed, instead the same port, channel, keyboard zone is used like for the forwarding function. The misc page provides the remaining parameters for the forwarding function (Octave transpose, optional Fx and Force-to-Scale) Hope that I haven't broken too much with the changes ;-) Best Regards, Thorsten.

Such as the MBSEQ V4L? ;-) Here a new version which supports recording - now the serious fun begins! :smile: -> http://www.ucapps.de/mios32/midibox_seq_v4_088_pre10.zip Again some limitations (it's only a quick&dirty hack to check the possibilities and blocking points): - live pattern recording should work flawlessly for drum tracks - it sometimes doesn't work correctly for common tracks if chords are played (the mechanism needs some logic to add/remove notes while key is pressed) - recording mode can be enabled in repeat page (it's the same function which is available in record page) - you can switch to EDIT page for visual check of the recorded pattern - required recording configuration: -- Rec Port/Channel have to match with Live Port/Channel; Fwd.Midi should be enabled -- if drums are recorded, one of the parameter layers (e.g. LayA) should be set to Velocity in the MENU->EVENT page (e.g. instead of Roll which is the default) It seems that I've to overwork the Rec/Live port & channel configuration. Actually they should be the same (I don't remember why I differentiated in the past...) Best Regards, Thorsten.

Cheers!

You are using a STM32F4! Of course, this changes the situation. The idle value is ok, same at my side with this core. Query is working at my side. Maybe the only difference: I'm using the latest bootloader Could you please update to the latest version (V1.018) as well? Since the query function doesn't work during runtime, you've to press&hold the blue button on the discovery board. Re-connect the USB cable Keep the blue button pressed! WinXP should install the USB MIDI driver for the bootloader (if this hasn't been already done) Restart MIOS Studio, select the right USB MIDI interface and upload the bootloader update application. All this by keeping the blue button pressed (to prevent that the MBSEQ app will be started) Release the blue button during the hex upload - the bootloader app will be started thereafter. Once the bootloader has been updated, upload the MBSEQ app Best Regards, Thorsten.

It works, but the travel is very limited, which means that it's difficult to set a specific velocity range with the key after it has been pressed. Polyphonic aftertouch values are sent, but they are more or less random... Best Regards, Thorsten.

It also crashes at my side. A quick analysis of the pattern data shows me that it's corrupted - I can't say why. Do you remember the moment when you stored the A7 pattern? Was there something special? (e.g. power interruption or similar?) I don't see an easy way to restore the pattern. In order to avoid the hang, you've to overwrite 2:A7 E.g. after power-on select group 2, press MENU+SAVE, select 2:A7, press the SAVE button and confirm the name. Best Regards, Thorsten.

Actually a great idea, so that I couldn't resist to hack this into the firmware: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre9.zip (Copy/Paste are available at GP15/GP16, and can also be executed with the dedicated buttons) But: accent won't be copied as the user might expect it. It will work if the track has enabled the accent trigger layer, if not the accent flags will get lost. The euclid generator doesn't get use of the accent flags, but directly sets the note velocity values instead to simplify the editing of a generated pattern. The "Live Pattern" copy/paste function would need a certain intelligence to determine this special situation, but it's too error prone... So: the copy&paste approach will only work reliable with gates. Best Regards, Thorsten.

Here the changes: http://svnmios.midibox.org/comp.php?repname=svn.mios&compare%5B%5D=%2Ftrunk%2Fapps%2Fprocessing%2Fmidibox_cv%2F%401033&compare%5B%5D=%2Ftrunk%2Fapps%2Fprocessing%2Fmidibox_cv%2F%40830 A V1.2c doesn't exist, and the changes between V1.2b to V1.3 don't explain the issue that you noticed. Could it be that you used a customized version, and therefore also changed the version number? To which pins are CLK and Start/Stop connected? According to this file: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidibox_cv%2Fsetup_j5_enabled.asm it's RC0 and RC1 Best Regards, Thorsten.

Previously you wrote that NUM_ENCODERS is 1, now encoder == 1 will be print (means: the second encoder, because encoders are counted from 0) However: remove (or disable) the encoder configuration and print debug messages from APP_DIN_NotifyToggle() instead - what happens? Best Regards, Thorsten.

This one should work: http://www.reichelt.de/AK-450/3/index.html?&ACTION=3&LA=446&ARTICLE=4012&artnr=AK+450&SEARCH=AK+450 Btw.: is it only me, or do you guys also have the impression that prices increased in the last weeks? E.g. my favorite turkish fast food restaurant recently increased the price for a Doner Kebab from 3.50 EUR to 4.50 EUR And now I notice that Reichelt increased the price for this cable from 3.50 EUR to 4.50 EUR as well! ;-) Best Regards, Thorsten.

The only explanation I have is, that your programming software overwrites the user id. Actually this would be nice, because then I'm sure that in this case the software also allows to set the user id to all-zero Where can I download the documentation about the software you are using? Best Regards, Thorsten.

Here another mockup: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre8.zip Instead of the repeat raster, a pattern can be selected. In the same page, the pattern can be edited by pressing (& holding) the SELECT button + the GP buttons (or encoders) I got rid of the idea to provide a "delay" trigger, because it conflicts with the already available groove function. So: it's better to use the groove function independent from the pattern selection. Instead, only gate and accent are editable. The "copy track to pattern" function isn't available yet, on the other hand it could complicate the handling too much. Of course, it would be nice to use it for taking over existing patterns, or transfer generated euclid patterns... On the other hand: where to place such a copy function? And is it really worth? I mean: a 16 gate/accent pattern is easy to remember, just enter it again with the pattern editor - something what don't has to be done so often, because I guess that once somebody found well working patterns, he won't edit them anymore. Best Regards, Thorsten.

With the pattern based approach a step offset wouldn't be required anymore (one reason why I find it useful :) The Euclidean generator could be used to generate a pattern. Usage could be the following way: create a pattern in EDIT page as usual (this allows you to use the euclid generator as well) Once you are happy with the pattern, transfer it into an ARP pattern slot and play it with the keyboard. Best Regards, Thorsten.

As mentioned by flyweight303, the feature would be more powerful if it would work like an arpeggiator. What I've in mind are 16 or 32 soft-configurable patterns with: - gates - accent - delay (for swing) how many steps would be required for such patterns? 8 or 16 or even 32? Memory consumption would be 3*(steps/8) bytes per pattern - no problem for STM32F4, could work with STM32F1 as well, but problematic for LPC17 (since RAM is almost fully allocated) But: for LPC17 I could at least provide pre-configured patterns (stored in flash) Best Regards, Thorsten.

Hi, D0 is located at pin 11, and D1 at pin 12 See also http://www.ucapps.de/mbhp/mbhp_dinx4.pdf It would be interesting if MIDIO128 outputs MIDI events if you turn the encoder (each pin should send an individual note event) Best Regards, Thorsten.

Hi, could you please pack the problematic session into a .zip file and attach it to this posting? Best Regards, Thorsten.

:phone:

Ok, try again with the latest sources in the repository (especially seq_midi_port.c) Best Regards, Thorsten.

The MIDI message shouldn't be sent immediately (it could be an option in future, but I added added some code which prevents this). Check your MIDI router and bus settings - only a single router node & MIDI bus should forward MIDI events. Best Regards, Thorsten.

Something overloads the CPU, this is indicated by the "system" command which shows 216% in your first snapshot. Actually it should be around 50% on a STM32F1 core (when no sequence is running) and around 60%..80% when the sequencer is running. I need more input: you've to find out, which configuration causes the overload - I can't help you to find this remotely... I know that there are many many many mode & parameters which could influence this (users requested so many features ;-)) - but at least I can say that you are using some kind of configuration which I haven't selected by myself in the past (I'm using a STM32F1 as well) It could make sense to start with a new session. Just enter "new <name-with-8-characters"> to create a new one If this already helps, then please attach your previous session directory to this posting. Best Regards, Thorsten.