TK.

MIDIbox SEQ V4 Release + Feedback

1,351 posts in this topic

Hi *,

this thread informs you about the latest release, and it gives you the possibility to write down your feedback (bug reports, questions about existing features, suggestions for new features, etc...)

The current MBSEQ V4 release can be downloaded from

http://www.ucapps.de/mios32_download.html

Please read the CHANGELOG.txt for latest changes

Documentation:

 

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Wohooo!

Too bad i've just packed all my gear for moving to a new flat  :(

Does this also mean the CORE_STM32 is available from SmashTV or Mike's ?

1 person likes this

Share this post


Link to post
Share on other sites

Wohooo!

Too bad i've just packed all my gear for moving to a new flat  :(

Does this also mean the CORE_STM32 is available from SmashTV or Mike's ?

Yes, from Smash TV.  :D

Share this post


Link to post
Share on other sites

Yes, the module and the optional kit is now available in SmashTV's Shop. :)

It won't be available in Mike's shop since it doesn't make much sense to distribute only the PCB w/o presoldered and tested STM32 chip.

Have fun! (Looking forward for more videos once your box has been upgraded! :))

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

This looks awesome, and I've ordered my Core32 from Smash!

I'm considering building a button/LED matrix as an addition to Wilba's panel.  I remember some discussion/speculation that V4 would allow for a bigger matrix.  Is that supported now?  If not, are there plans to support more buttons/LEDs in a future V4 release?

Share this post


Link to post
Share on other sites

Hey TK, just out of interest, is Midi Clock supported for the other Midi Out? What about the IIC modules?

Regards

Mike

Share this post


Link to post
Share on other sites

I'm considering building a button/LED matrix as an addition to Wilba's panel.  I remember some discussion/speculation that V4 would allow for a bigger matrix.  Is that supported now?  If not, are there plans to support more buttons/LEDs in a future V4 release?

As described at the User Manual: Hardware page, the 4x16 BLM is already supported.

For future, I consider to create a new 16x16 button/LED matrix, this time built on a PCB to avoid all the soldering effort. Probably it will be based on MAX7221 chips as serial shift registers and LED driver. Once I have the hardware, I can add a sophisticated SW support. I'm planning a lot of functions for such a matrix, like direct drum track editing (all 16 instruments in a view), direct track mutes editing (all 16 tracks in a single view), setting loop points, alternative pattern selection (as 256 buttons are available), etc...

It's even feasible to cascade 16x16 matrices to a giant display ;)

Hey TK, just out of interest, is Midi Clock supported for the other Midi Out? What about the IIC modules?

MIDI Clock can be sent by any MIDI port, and it can be enabled individually as described at the User Manual: Menu Pages

IIC: 4 modules are natively supported, the usage of 8 modules is feasible (with a firmware hack) as described at the User Manual: Hardware page

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Beta2 is available now.

From the ChangeLog:


     
  • Song page got a copy/pase/clear/insert/delete function for song steps.[br]
        Press the SELECT button to select the utility function
     
  • Copy/Paste/Clear button can be used in song page as well
     
  • Song/Phrase mode not switched via SONG button anymore (this handling
        is an artifact from MBSEQ V2/V3)[br]
        Instead, the mode can be changed with GP encoder #8 or #9
     
  • a 16 step selection pattern for the ALL function is now available
        (only selected steps will be touched by the ALL function).[br]
        It can be changed by pressing the SELECT button in EDIT page.
     
  • the 16 instrument labels of a drum track can be edited now
     
  • a nice graphical logo is now print during startup
     
  • lower CPU load if no SD Card connected

The new pages are also described in the User Manual: Menu pages.

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Hey TK I know its still beta and am not complaining but hopefully helping by addressing these. For some reason I have had patterns that I want to change the length from 16 to 32 or 64 steps and it won't work. It just keeps cycling 1-16. On one instance I had a pattern play the first 8 steps then play the whole 16 steps then the just the first 8 again and so on and so on in a logical pattern. Did I do this somehow?

Also the echo fx would sometimes not work or have a 7-8 second delay before they kick in. It seemed like a processing time loading issue. I am talking about the repeat #. I would try it from 1-15 and not get anything.

I noticed when you tap the mute button, the "parameter selection" page flashes on for a quick second.

When I was testing V3, regarding the 3 layers gate,vel and length for example I could press the length parameter button and then turn the knobs to get the desired note length but now in v4 I press the length button and get another page of all the parameters and must press an additional button to get there. Is this normal?

I'll post what ever I can and I will try to be more detailed.

The sequencer kicks major booty if any one wants to know.:)

Oh and I was jamming with a friend and when you get to excited you can accidentally hit the clear track button on wilbas panel right below step 7. Can you make it so you have to press the clear button twice to confirm and then clear the track?

Hope this info helps.

Share this post


Link to post
Share on other sites

Hey TK I know its still beta and am not complaining but hopefully helping by addressing these. For some reason I have had patterns that I want to change the length from 16 to 32 or 64 steps and it won't work. It just keeps cycling 1-16. On one instance I had a pattern play the first 8 steps then play the whole 16 steps then the just the first 8 again and so on and so on in a logical pattern. Did I do this somehow?

There is no reason why the length parameter shouldn't work.

Could it be that the loop function was activated? (Fx->Loop)

Also the echo fx would sometimes not work or have a 7-8 second delay before they kick in. It seemed like a processing time loading issue.  I am talking about the repeat #. I would try it from 1-15 and not get anything.

There shouldn't be a processing time issue.

How can I reproduce this exactly? (describe the configuration steps)

I noticed when you tap the mute button, the "parameter selection" page flashes on for a quick second.

Didn't you request the possibility to mute parameter layers?

Or who was it? ;)

When I was testing V3, regarding the 3 layers gate,vel and length for example I could press the length parameter button and then turn the knobs to get the desired note length but now in v4 I press the length button and get another page of all the parameters and must press an additional button to get there. Is this normal?

Yes, so long more than 4 parameter layers are configured.

I guess you configured it for 8 or 16?

If a track only consists of 4 parameter layers, ParLayer C button will toggle between layer C and D

Oh and I was jamming with a friend and when you get to excited you can accidentally hit the clear track button on wilbas panel right below step 7. Can you make it so you have to press the clear button twice to confirm and then clear the track?

Doubleclicks won't really help - I could insert a delay (press button for more than 2 seconds)

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Doubleclicks won't really help - I could insert a delay (press button for more than 2 seconds)

I think 2 sec delay sounds good.

Share this post


Link to post
Share on other sites

BLM MATRIX PROBLEMS on SEQ V4:

Just finished updating my SEQ to V4.

Everything works perfect except one thinng:

The LEDs on my BLM seem to be wrong adressed.

On an empty pattern all LEDs on the four tracks are off. Ok so far.

But when I set one step, the LEDs of the the wrong Track is set or the other tracks are inverted.

(e.g. i set step 9 on track 2 -> step 9 on tracks 1,3,4 LED on track 2 stay off)

(or if i set a step on Track 3 the LED on Track 1 will be inverted)

(lots of more strange effects on the BLM LEDs...)

The chaselight works partly correct on all four Tracks, with the exception that on active steps

the LED does not go off but stays on.

The Buttons on the matrix work 100% right!

(same effect if I use matrix or GP buttons to set steps)

(the BLM worked right with SEQ V3, no hardware changes during update to V4)

I use sinkdrivers for the Cathodes, but it makes no difference whether I set the Inversion Mask 0x00 or 0xf0.

Behaviour of the LEDs is the same with both settings!

(I know that my configfile is loaded as all customized button/LED assignments work)

So my question: Is the BLM not fully supported yet?

Or any suggestions what could be wrong?

Best regards

Gridracer

EDIT: specified error description

here my MBSEQ_HW settings:

##################################################
# Setup File for Chainreactor Frontpanel
# $Id: MBSEQ_HW.V4 630 2009-06-28 20:24:53Z tk $
##################################################


##################################################
# Shift Register Setup
##################################################

# number of first and second DOUT shift register used for GP LEDs
GP_DOUT_L_SR    3
GP_DOUT_R_SR    4

# DOUTs for Dual Color option:
GP_DOUT_L2_SR  0
GP_DOUT_R2_SR  0


##################################################
# Optional BLM Matrix
##################################################

# set this value to 1 if each track has its own set of 16 LEDs to display unmuted steps and current sequencer position
# or if you are using a button/led matrix for misc. button/LED functions
BLM_ENABLED     1

# define the shift registers to which the anodes of these LEDs are connected
# Note: they can be equal to GP_DOUT_[LH]_SR, this saves two shift registers, but doesn't allow a separate view of UI selections
BLM_DOUT_L1_SR	6
BLM_DOUT_R1_SR	7

# define the shift register to which the cathodes of these LEDs are connected
# Note that the whole shift register (8 pins) will be allocated! The 4 select lines are duplicated (4 for LED matrix, 4 for button matrix)
# The second DOUT_CATHODES2 selection is optional if LEDs with high power consumption are used - set this to 0 if not used
BLM_DOUT_CATHODES_SR1  5
BLM_DOUT_CATHODES_SR2  0

# set an inversion mask for the DOUT shift registers if sink drivers (transistors)
# have been added to the cathode lines
# Settings: 0x00 - no sink drivers
#           0xf0 - sink drivers connected to D0..D3
#           0x0f - sink drivers connected to D7..D4
BLM_DOUT_CATHODES_INV_MASK 0xf0

# 0: no DUO colour LEDs are connected to the LED matrix (position marker inverts step LED)
# 1: DUO colour LEDs are connected to the LED matrix, second LED displays position marker
# 2: Like option 1, but the first LED is turned off when the position marker activates the second LED
BLM_DOUT_DUOCOLOUR  0

# define the shift registers to which the anodes of the "second colour" (red) LEDs are connected
BLM_DOUT_L2_SR  0
BLM_DOUT_R2_SR  0

# set this to 1 if a button matrix is connected
BLM_BUTTONS_ENABLED 1

# set this to 1 if these buttons should only control the "step triggers" (gate, and other assigned triggers) - and no UI functions
BLM_BUTTONS_NO_UI   1

# define the DIN shift registers to which the button matrix is connected
BLM_DIN_L_SR  6
BLM_DIN_R_SR  7



##################################################
# Additional 8x8 BLM as used for Wilba's Frontpannel
##################################################

# set to 1 to enable 8x8 BLM driver
BLM8X8_ENABLED  0

# to which shift register are the select lines connected?
# Allowed values: 0 to disable, 1..16 to assign shift register
BLM8X8_DOUT_CATHODES_SR  0

# set an inversion mask for the DOUT shift registers if sink drivers (transistors)
# have been added to the cathode lines
BLM8X8_DOUT_CATHODES_INV_MASK 0x00

# to which shift register are the LED anode lines connected?
# Allowed values: 0 to disable, 1..16 to assign shift register
BLM8X8_DOUT_LED_SR	0

# 0: no mapping of 8x8 LEDs
# 1: enable GP LED -> 8x8 matrix mapping for Wilba's MB-SEQ PCB
BLM8X8_DOUT_GP_MAPPING  0

# 8x8 matrix for misc. button functions
BLM8X8_DIN_SR  0


##################################################
# CV and Gate/Trigger/Sync Setup
##################################################

# define the AOUT interface which is connected to the core
#  1: a MBHP_AOUT module
#  2: up to 4 (chained) MBHP_AOUT_LC modules in 8/8 bit configuration
#  3: a MBHP_AOUT_NG module
AOUT_INTERFACE_TYPE 1

# additional gate triggers are available on common digital output pins of the
# DOUT shift register chain - they are assigned to AOUT channel #16 (Note C-1, C#1, D-1, ...)
# define the shift registers which should be used here (each provides 8 gates)
# Note that SRs assigned to this function cannot be used as LED outputs (exclusive function)
# Allowed values: 1-16, 0 disables the function, all other values invalid and not allowed
DOUT_GATE_SR1   0
DOUT_GATE_SR2   0
DOUT_GATE_SR3   0
DOUT_GATE_SR4   0
DOUT_GATE_SR5   0
DOUT_GATE_SR6   0
DOUT_GATE_SR7   0
DOUT_GATE_SR8   0

# if set to 1, the DOUT "gates" will send 1mS pulses
# useful for analog drums
DOUT_1MS_TRIGGER 0

# should J5A/B/C outputs be enabled (0: no, 1: yes, 2: yes, but in open drain mode)?
#  - the 8 AOUT gates will be forwarded to J5A/B
#  - DIN sync clock will be forwarded to J5C:A0
#  - DIN sync start/stop will be forwarded to J5C:A1
#  - if open drain mode enabled (option 2), external pull-ups have to be connected to J5 pins
#    (advantage: pin levels can be pulled to 5V)
#
# NEVER USE THIS TOGETHER WITH ANALOG POTS - IT WILL CAUSE A SHORT CIRCUIT!
J5_ENABLED 0


##################################################
# LED assignments to DOUT pins
# SR = 0: LED disabled
# SR = 1..16:  directly forwarded to DOUT pin
# SR = 17..24: forwarded to a 8x8 LED matrix
##################################################

#           SR  Pin
LED_TRACK1   1   0
LED_TRACK2   1   1
LED_TRACK3   1   2
LED_TRACK4   1   3

#                SR  Pin
LED_PAR_LAYER_A   1   4
LED_PAR_LAYER_B   1   5
LED_PAR_LAYER_C   1   6

#         SR  Pin
LED_BEAT   1   7

#           SR  Pin
LED_EDIT     2   0
LED_MUTE     2   1
LED_PATTERN  2   2
LED_SONG     2   3

#           SR  Pin
LED_SOLO     2   4
LED_FAST     2   5
LED_ALL      2   6

#           SR  Pin
LED_GROUP1  8   0
LED_GROUP2  8   1
LED_GROUP3  8   2
LED_GROUP4  8   3

#                SR  Pin
LED_TRG_LAYER_A   9   0
LED_TRG_LAYER_B   9   1
LED_TRG_LAYER_C   9   2

#           SR  Pin
LED_PLAY     9   3
LED_STOP     9   4
LED_PAUSE    9   5
LED_REW     10   3
LED_FWD     10   4
LED_LOOP     0   0

#               SR  Pin
LED_EXIT        10   5
LED_SELECT      10   6
LED_MENU        10   7
LED_SCRUB       10   2
LED_METRONOME    0   0
LED_RECORD       8   4
LED_UTILITY      8   7
LED_COPY         8   6
LED_PASTE        8   5
LED_CLEAR        0   0

#                  SR  Pin
LED_STEP_VIEW       9   7
LED_PAR_LAYER_SEL   0   0
LED_TRG_LAYER_SEL   0   0
LED_TRACK_SEL       9   6

#                  SR  Pin
LED_TAP_TEMPO       0   0
LED_TEMPO_PRESET    0   0
LED_EXT_RESTART     0   0

#         SR  Pin
LED_DOWN   0   0
LED_UP     0   0



##################################################
# Button assignments to DIN pins
# SR = 0: Button disabled
# SR = 1..16:  directly triggered from DIN pin
# SR = 17..24: triggered from a 8x8 button matrix
##################################################

#            SR  Pin
BUTTON_DOWN   1   0
BUTTON_UP     1   1
BUTTON_LEFT   0   0
BUTTON_RIGHT  0   0

#                 SR  Pin
BUTTON_SCRUB       1   7
BUTTON_METRONOME   0   0
BUTTON_RECORD     13   1

#             SR  Pin
BUTTON_STOP    11   2
BUTTON_PAUSE   12   1
BUTTON_PLAY    12   7
BUTTON_REW     11   7
BUTTON_FWD     13   6
BUTTON_LOOP    0   0

#              SR  Pin
BUTTON_MENU     11   0
BUTTON_SELECT   12   0
BUTTON_EXIT     13   0

#              SR  Pin
BUTTON_TRACK1   2   3
BUTTON_TRACK2   2   5
BUTTON_TRACK3   2   2
BUTTON_TRACK4   2   6

#                   SR  Pin
BUTTON_PAR_LAYER_A  11   4
BUTTON_PAR_LAYER_B  11   3
BUTTON_PAR_LAYER_C  11   5

#                SR  Pin
BUTTON_EDIT      11   6
BUTTON_MUTE       2   0
BUTTON_PATTERN   12   3
BUTTON_SONG      12   4

#            SR  Pin
BUTTON_SOLO   2   7
BUTTON_FAST   1   6
BUTTON_ALL    2   1

#            SR  Pin
BUTTON_GP1    3   0
BUTTON_GP2    3   1
BUTTON_GP3    3   2
BUTTON_GP4    3   3
BUTTON_GP5    3   4
BUTTON_GP6    3   5
BUTTON_GP7    3   6
BUTTON_GP8    3   7
BUTTON_GP9    8   0
BUTTON_GP10   8   1
BUTTON_GP11   8   2
BUTTON_GP12   8   3
BUTTON_GP13   8   4
BUTTON_GP14   8   5
BUTTON_GP15   8   6
BUTTON_GP16   8   7

#              SR  Pin
BUTTON_GROUP1  2   4
BUTTON_GROUP2  1   4
BUTTON_GROUP3  1   3
BUTTON_GROUP4  1   5

#                   SR  Pin
BUTTON_TRG_LAYER_A  12   5
BUTTON_TRG_LAYER_B  12   2
BUTTON_TRG_LAYER_C  12   6


# Following button functions are usually assigned to Fx
# buttons, or to dedicated (labeled) buttons
# In the standard frontpanel layout:
# F1 is located at SR 13 Pin 4
# F2 is located at SR 13 Pin 2
# F3 is located at SR 13 Pin 5
# F4 is located at SR 13 Pin 1

#                    SR  Pin
BUTTON_UTILITY       13   4
BUTTON_STEP_VIEW     11   1
BUTTON_TRG_LAYER_SEL  0   0
BUTTON_TRACK_SEL     13   7

BUTTON_PAR_LAYER_SEL  0   0

#                    SR  Pin
BUTTON_TAP_TEMPO     13   3
BUTTON_TEMPO_PRESET   0   0
BUTTON_EXT_RESTART    0   0

#                SR  Pin
BUTTON_COPY      13   2
BUTTON_PASTE     13   5
BUTTON_CLEAR      0   0


#                SR  Pin
BUTTON_MORPH      0   0
BUTTON_MIXER      0   0
BUTTON_TRANSPOSE  1   2


##################################################
# Button behaviour
# 0: active mode so long button pressed
# 1: pressing button toggles the mode
##################################################

BUTTON_BEH_FAST         1
BUTTON_BEH_ALL          1
BUTTON_BEH_SOLO         1
BUTTON_BEH_METRONOME    1
BUTTON_BEH_LOOP         1
BUTTON_BEH_SCRUB        0
BUTTON_BEH_MENU         1
BUTTON_BEH_STEP_VIEW    1
BUTTON_BEH_TRG_LAYER    1
BUTTON_BEH_PAR_LAYER    1
BUTTON_BEH_TRACK_SEL    0
BUTTON_BEH_TEMPO_PRESET 0


##################################################
# Special Behaviour of ALL button
# 0: only all parameter layers are modified
# 1: all trigger and parameter layers are modified
##################################################
BUTTON_BEH_ALL_WITH_TRIGGERS 0


##################################################
# Encoder Functions
# SR = 0: encoder disabled
# SR = 1..16: DIN assignment
# Types: NON_DETENTED, DETENTED1, DETENTED2, DETENTED3
##################################################

#              SR  Pin  Type
ENC_DATAWHEEL   1   0   DETENTED2

# the speed value for the datawheel which is used when the "FAST" button is activated:
ENC_DATAWHEEL_FAST_SPEED 3

#         SR  Pin  Type
ENC_GP1    4   0   DETENTED2
ENC_GP2    4   2   DETENTED2
ENC_GP3    4   4   DETENTED2
ENC_GP4    4   6   DETENTED2
ENC_GP5    5   0   DETENTED2
ENC_GP6    5   2   DETENTED2
ENC_GP7    5   4   DETENTED2
ENC_GP8    5   6   DETENTED2
ENC_GP9    9   0   DETENTED2
ENC_GP10   9   2   DETENTED2
ENC_GP11   9   4   DETENTED2
ENC_GP12   9   6   DETENTED2
ENC_GP13  10   0   DETENTED2
ENC_GP14  10   2   DETENTED2
ENC_GP15  10   4   DETENTED2
ENC_GP16  10   6   DETENTED2

# the speed value for GP encoders which is used when the "FAST" button is activated:
ENC_GP_FAST_SPEED 3

# Auto FAST mode: if a layer is assigned to velocity or CC, the fast button will be automatically
# enabled - in other cases (e.g. Note or Length), the fast button will be automatically disabled
ENC_AUTO_FAST        1

Share this post


Link to post
Share on other sites
Didn't you request the possibility to mute parameter layers?

I didn't even know that was possible. Do you just hold down the mute key and press some gp buttons to mute the layers?

I guess you configured it for 8 or 16?

If a track only consists of 4 parameter layers, ParLayer C button will toggle between layer C and D

I was using the default setting. I'll have to check this out. Too much good stuff.

I am wondering if its possible to set the fx parameters for each individual step and not just the whole track in general? I noticed there is a mute fx parameter. Would I just have to fx mute all the steps I don't want the repeat,lfo ect on? My first thought was in the fx page to use the 16 steps to select the step you want to edit and the echo/lfo page will switch between the different step settings as you enable the respective step.

Would any one else find this useful?

and as far as the slow processing time I will have to get back to you. Maybe it is a usb issue and my pc  ;)

Share this post


Link to post
Share on other sites

I use sinkdrivers for the Cathodes, but it makes no difference whether I set the Inversion Mask 0x00 or 0xf0.

Behaviour of the LEDs is the same with both settings!

The BLM driver is completely implemented, but the inversion mask wasn't changed.

I fixed this in beta3

I didn't even know that was possible. Do you just hold down the mute key and press some gp buttons to mute the layers?

Yes, to mute individual parameter layers.

Thats especially useful if a track plays drum instruments - you can mute individual drums.

This function is described under User Manual: Menu Pages

I am wondering if its possible to set the fx parameters for each individual step and not just the whole track in general? I noticed there is a mute fx parameter. Would I just have to fx mute all the steps I don't want the repeat,lfo ect on? My first thought was in the fx page to use the 16 steps to select the step you want to edit and the echo/lfo page will switch between the different step settings as you enable the respective step.

Haha ;) no, this isn't possible - it would require a *huge* pattern memory to store the parameters for each step.

Not only that the appr. SRAM space isn't available... it would also increase the time to change to a new pattern dramatically!

However, once the Loopback function does also work for Sequencer Parameters (CCs), you will be able to change up to 16 Fx parameters per track for each individual step! I think that this will really cover your request.

Beta3 is available now - from the ChangeLog:

[tt]

 o if global loop mode enabled, a "*LOOPED*" message will flash at the

   right corner of the EDIT and STEPVIEW screen.

 o following handling has been added to realize a "smooth startup" for

   people who are in the progress of building their MBSEQ. The core is already

   running, they connect a SD Card but don't have LCDs (so that messages

   cannot be read):

     - if a SD Card without Banks/Songs/Mixer Maps is connected, the appr.

       files won't be created automatically anymore.

     - messages are print on the PATTERN/SONG and MIXER page to inform

       that files have to be created from the UTILITY->DISK menu

     - in the DISK->UTILITY menu you will find a special option at the left

       side which allows to start the formatting process (in fact, the SD

       Card won't be formatted, but some files will be created)

     - there is now a nice progress bar which informs about the state

       so long formatting is in progress

 o CLEAR button has to be pressed for 2 seconds before action is triggered

 o fixed BLM inversion mask configuration

[/tt]

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites
once the Loopback function does also work for Sequencer Parameters (CCs), you will be able to change up to 16 Fx parameters per track for each individual step! I think that this will really cover your request.

ooooo :D yes yes yes please elaborate!

Can I guess all this is done by selecting your parameter layer with the correct cc on it. as an example take the echo repeat cc and set the steps to value 0 for off and 1 for 1 repeat, 2 for 2 repeats and so on? And then I can even do more cc parameter layers for the echos feedback, velocity, signature ect..?

Share this post


Link to post
Share on other sites

Can I guess all this is done by selecting your parameter layer with the correct cc on it. as an example take the echo repeat cc and set the steps to value 0 for off and 1 for 1 repeat, 2 for 2 repeats and so on? And then I can even do more cc parameter layers for the echos feedback, velocity, signature ect..?

Yes, it's even possible to modulate sequencer parameters via LFO

E.g., during this experiment I controlled the amplitude of LFO Track #1 (sine waveform with 8 steps interval) with the LFO of Track #2 (saw waveform with 64 steps interval)

Track #1 plays note events + an echo Fx, force to scale has been activated.

That's called amplitude modulation :)

mbseq_lfo_am.png

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Hi TK,

just installed Beta3 and slowly getting familiar with the Seq. I am just wondering some things given wilba's FP design):

a) i can select A-C in the trigger layer, is there a way to change the assignment what is on the individual layers ? I managed to see the different

assignments in a menu but weren't unable to actually change those.

b) Given the Sequencer as Master and Ableton Live (instrument) as slave with a instrument, is there a way to "create" the CC messages (e.g. for Filter Control)

using a defined encoder for the whole track ? e.g drawing the filter curve.

c) with regards to b) single creation of a CC event when i enabled the "Learn" mode of a instrument ?

not sure if that is fully implemented (yet) or planned, but this would be a nice addon.

Share this post


Link to post
Share on other sites

SOLVED: BLM MATRIX PROBLEMS on SEQ V4

just uploaded Beta 3 and now the matrix works fine!

Thanks TK!

Best Regards

Gridracer

Share this post


Link to post
Share on other sites

a) i can select A-C in the trigger layer, is there a way to change the assignment what is on the individual layers ? I managed to see the different

assignments in a menu but weren't unable to actually change those.

Press MENU->TRIGGER (GP Button #9) to change the trigger assignments.

Note that in distance to MBSEQ V4 we have 8 trigger layers now (A..H) - the 8 available triggers functions are assigned to A..H, accordingly they can all be used in a pattern.

Changing the assignments only makes sense if you prefer a different order (e.g. Glide assigned to B instead of D), or if you want to trigger multiple functions with a single trigger (e.g. if Trigger A should activate Glide and Random Velocity)

b) Given the Sequencer as Master and Ableton Live (instrument) as slave with a instrument, is there a way to "create" the CC messages (e.g. for Filter Control)

using a defined encoder for the whole track ? e.g drawing the filter curve.

Just change to the Mixer page (MENU->Mixer), and use the datawheel to select the CC page

Each page provides 16 CCs, there are 4 pages (accordingly, 64 CCs can be defined)

By pressing the SELECT button you can store your mixer configuration in a Mixer Map

c) with regards to b) single creation of a CC event when i enabled the "Learn" mode of a instrument ?

The required procedure should be described in the user manual of Ableton Live.

It works great with Logic :)

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

EXIT LED BUG

just toyed around with V4Beta3 and noticed that there is a little bug with the Exit LED:

EXIT LED will not go on when the EXIT button is pressed, but depressing the EDIT button will cause it to

light. (EDIT LED works right, EDIT and EXIT button call the right menu page)

I think I can exclude a hardware issue as it does not matter to what shift register nr. and pin nr. I connect the EXIT LED  and assign it in the setup file, the effect stays the same.

Best Regards

Gridracer

Share this post


Link to post
Share on other sites

I never used an EXIT LED by myself... ;)

Will be fixed in beta4 (release this evening).

Next bug, please.

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Beta4 is available for download.

ChangeLog:

[tt]

 o MBSEQ Parameters are controllable via NRPN messages from external MIDI devices now.

   See also doc/mbseqv4_cc_implementation.txt

 o these parameters can also be controlled via Internal Loopback (Bus1 Port).

 o Loopbacked CC Parameters are print in text format when edited

 o implemented MIDI Remote Keyboard function (note: MBSEQ_HW.V4 has been updated)

   See also doc/mbseqv4_remote_functions.txt

 o fixed various minor bugs

[/tt]

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites
I never used an EXIT LED by myself... Wink

I wouldn't either but all of my Buttons have an LED by default....

so why not use them... and I really like the buttons to glow...  ;)

Next bug, please.

-Well, now the EXIT LED does not work at all

EDIT: removed entry about EDIT LED (user error)

Finally,

i would like to ask for a TRANSPOSE LED in some future release. Shame on me!

It is the only LED one not in us on my entire Frontpanel ... so just for the bling...

->super super low priority

Best regards Gridracer

Share this post


Link to post
Share on other sites

Ok, EXIT LED is now active whenever the menu selection page is displayed - this makes more sense anyhow.

And for the bling I added a Morph/Mixer/Transpose LED function.

Will be available in beta5.

Best Regards, Thorsten.

Share this post


Link to post
Share on other sites

Ok i had a suggestion for a new content on the lenght dialog on the Lenght page. It is possible, to fill the empty Space in the Left Display behind the Button 4 labled with Loop 1

In order to use a Quick selection for Looppoints i would be nice when i had a few points more in the dialog

On Step 5 labeld with Looppoint 9 means when i push GP Button 5  it will be loop the Step 9 - 16 immediatly

Example:

On GP Button 7  Loop at 9  .... that will be Loop the Steps 9 - 16

On GP Button 6  Loop at 17 .... that will be Loop the Steps 17 - 24

On GP Button 7  Loop at 25 .... that will be Loop the Steps 25 - 32

On GP Button 8  Loop at 33....  that will be Loop the Steps 33 - 40

For me i think that´s ok for the most common Step Lenght at max 32 Steps that i use.

The Name can be  Quick Loop Points or so !    There a 19 charakters left on this empty field!

I hope that would be possible ......

Have a nice Day,

Marco

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now