Rio

TK wrote: Hey Tk, your post is a long time ago, but did you still knew, how you had filled up the arp sequence for that case? Have you used Chords or Notes as eventtype (and track mode: normal, transposed or arp?) and which track parameter have you used and configured for that? It sounds clear and good! Did you added additional notes as track parameter inside that chord sequence too? (0-3-7 / 0-4-7 as major / minor) Greetings, rio

Thanks for your fast hint. Great, now everything is working fine.

hey tk, sorry, i can not compile v.4079 - I have updated my mios32 svn directory, since MBSEQV4 version 4.078, which had compiled fine. Please take a look at the screenshot in attachment.

Cool ;) go ahead for a full bank. Thank you.

that is comprehensible.. thanks for the new version v.4079

Nice demonstration. Beside, would it be possible to integrate a second LFO? Or would that to much loading for the cpu? Often i want to change reso + cutoff with different LFOs at the same time. Best regards, rio

i use my seqv4 in pattern mode. Patterns, Mixermaps will be changed from another external application. Greetings.

Her eyes are only dedicated to you! :D

hi blingy, it is simple a MIDI Controller and e.g. therefor you are able to load the correct instrument mappings. You can send out your defined CC/Prog.Changes via dump to your defined Ports. Best regards, rio

Excellent!! Thanks. Rio

Hello TK, I have small request for a behaviour, which I have noticed: A Patternchange will ignore the new CC values of a track, when another track changed that CC values through an LFO which are send out as FastCC. For example, i am playing a track with #CC40 as Parameter and constant values 34 for each step. Then I changed to a track which used a "Saw" LFO for #CC40, so that it will uplift the values for that CC with offset 34 (e.g. values from 34 .. to 47). Then I changed back to track, which does contains the #CC40 as Parameter with constant values 34 for each step again, but it will not send out again that value 34 (it stays at 47 instead) Since SEQV4 will only send out changed CC values, I believe that the values which was changed through LFO will not noticed for that "track parameter changing". My SEQV4 setup: patternchange synchronizing enabled patternchange synchronizing 16 step Restart all track on pattern changed enabled I hope my explanation is understandable. Greetings, rio

hi george, inside this document, you will find detailed information of the LPC17 connectors: http://www.ucapps.de/mbhp/mbhp_core_lpc17_pcb_v1_0.zip Have fun building your seqv4 ;) greets, rio.

Necessary PDF documents from the LPC17 based core page: http://www.ucapps.de/mbhp/mbhp_core_lpc17.pdf from the MIDIbox SEQ V4 -->User Manual -->Hardware Options Page: http://www.ucapps.de/midibox_seq/mbseq_v4_din.pdf http://www.ucapps.de/midibox_seq/mbseq_v4_dout.pdf http://www.ucapps.de/mbhp/mbhp_core_lpc17_midi3_midi4_extension.pdf from the SD Card Page: http://www.ucapps.de/mbhp/mbhp_sdcard.pdf Greetings, rio.

Hi George, please Take a Look at the MBSEQV4 Site --> Tutorials --> Hardware Options. Everything is well documented, also PDF documents for interconnection to Sdcard, iic, DINX and DOUTX. Greetings, Rio.

wow. fine ;) thanks again.

Could it be a Bootloader message? Greets,

Hi Community, a) I see that the additional CCs of "Mixer Map" are assignable in a range of 0 to 112. Is there a reason for that purpose (not max 127 (0x7F))? b) if the sequencer is running then multiple dump-calls of mixermaps will hang up the application (and sometimes the send routine will cause a delay for sending that mixermap in contrast to MBSEQV3). c) I miss the cc 111 implementation to dump a special mixer map, like it was implemented in SEQV3 (I would be glad if that could be adapted :smile: ): CC#111 (0x6f) Dumps the values of a Mixer map (0..127) little request in that mixermap section: I don't know, if you like the feature, that the user can decide whether any of these additional CCs (1-4) could send before all the standard Mixer CCs (like Prog.Change) will send out, so that e.g. Bank.Change Commandos (CC 0 and/or CC 32) can be supported by that mixermap (so that it will send out ahead of Prog.Change). c) the manual of V4 at point "Pattern Screen" says: GP buttons: the 128 patterns are enumerated from A1 to h8. The 8 buttons at the left side switch between A-H/a-h (press the button twice to select a "lower case" character), the 8 buttons at the right side are used to select the pattern number (1-8). ..but I can only choose between A..H and not lowercase Patterns. Is it a bug or are there now only patterns from A to H possible for a bank? d) incomming MIDI CC will be only recognized if Ext.Ctrl -> IN is not set to "ALL" hey tk, don't take all my suggestions/reports as negative points - that new application is a superb application and i am impressed again! So big thanks! and a lot of success & fun on doing this. Greets, rio

Hi TK, a big thanks to you from me! for the new Midibox SEQ V4 upgrade, which I had finished last days! The application looks great and a lot of points look very similar to SEQV3, which makes my life easier ;) Go ahead! I like also the little gimicks like loader screen etc. big thx and Greets, rio

Hi all, i have build up the BPM LED digits exactly like: http://www.ucapps.de/midibox_seq/mbseq_v4_bpm_digits.pdf but i'm not sure how to setup it correct, because all LEDs of every segment are "on", when I start and run a sequence. I use these 7 segment digits: http://www.dl9usa.de/Ebay/009/vqb37.gif and these MBSEQ_HW.V4 settings (which must be wrong :D): ################################################## # Optional BPM digits ################################################## # set to 1 or 2 to enable the 3 optional BPM digits # 0: BPM digits disabled # 1: BPM digits with common cathode # 2: BPM digits with common anode BPM_DIGITS_ENABLED 1 # define the DOUT shift register to which the segments are connected (0=disabled) BPM_DIGITS_SEGMENTS_SR 5 # define the DOUT SR and pin to which the common pins are connected # we are counting from right to left # Example: 140.5 BPM: (COMMON1 = .5, COMMON2=0., COMMON3=4, COMMON4=1) # SR Pin BPM_DIGITS_COMMON1_PIN 4 3 BPM_DIGITS_COMMON2_PIN 4 2 BPM_DIGITS_COMMON3_PIN 4 1 BPM_DIGITS_COMMON4_PIN 4 0

thx correct, i have found a short cut on sd card mount. so Vs was connected to Vcc. greets, rio

Hello, is it normal that LF33 will be very hot in a short time when I connect a SD Card to J16? There is only the bootloader installed and after inserting SD Card -> the LCD shines a bit weaker and Core's LED switched of and it restarts after removing SD Card again. With Card inserted the core won't complete boot. The core gets power via external 5V. Thanks for help. Greets, rio

hey thx, LED_MIDI_OUT_COMBINED / LED_MIDI_IN_COMBINED is a common - "not port-depended" - indicator. correct? Greets ,rio

Hello, i need help - where should I connect Tx and Rx LEDs for MIDI IN 1 2 3 4 and MIDI Out 1 2 3 4 (similar to IIC Tx/Rx)? Which port/connector can i use? PS: I found something about MIDI 3 OUT/IN in this document http://www.ucapps.de/mbhp/mbhp_core_lpc17_output_buffers.pdf but I don't kn whether its for LEDs Output. Thx for any help. Greets, rio