jjonas

I have them, but I've never really used them. Mine are log. I haven't noticed any noise problems. With pot shafts and knobs I think you've got knurled shafts, round smooth shafts and D-shaped shafts. Knurled shafts don't have tightening screws on them, but smooth ones do. Of D-shaft ones I'm not sure, I think they tend to use push-on knobs, so no screw. Note also that the diameter of length of the shafts may vary; e.g. diameter can be 6.0mm or 6.3mm, and while you can fit a 6.3mm knob (with a screw) on a 6mm shaft, it won't be completely centered. Knurled shafts tend to be split (to facilitate a push-on knob), but smooth ones are always solid (as far as I can tell) and need a knob with a tightening screw. I have knurled shaft pots with push-on knobs. It was years ago when I built my MB6582, but I think the screws came with the PacTec case. I used JST connectors, but only because I have them (and the crimp tool) available at work. The biggest threshold for JST is probably the insane price of the crimpi tool itself, at least the JST original. I wasn't able to find a knock-off that would have crimped them adequately. I tried two cheaper models but neither of them worked properly on JST, so I'm using Dupont connectors nowadays for my projects. The advantage of JST though is that it's about 50% more shallow than Dupont, and I'm not sure if Duponts would fit in the space available in the PacTec case.

@ChinMuzik You can check on the shop website whether your order has been shipped or not. In my experience a month's waiting time is normal. http://midiboxshop.bigcartel.com/shipping-status

On MBSEQv4 this function is called 'scroll', which is found in the UTILITY menu. From the Beginner's Guide (section 4.2.2.): "Scroll allows you to move sections of steps with the knobs. When you press & hold 'Scroll', the screen switches to the EDIT page, and you can use a GP knob to grab a section of steps, so that the steps to the right of the knob (including the one above the knob) will be moved together, while the ones to the left will stay where they are. Releasing the GP button writes the moved steps into the new location, overwriting whatever was there previously. "

Is this section in the Beginner's Guide helpful? (EDIT: for understanding 'Take over Patterns'.) "On the PATTERN page you can select the four patterns that you need and see their names while you do the selection. (Naturally this requires that you've given your patterns a category and a label when you've saved them individually earlier.) After selecting the desired pattern for each group, you can press & hold SONG to select 'Take Over Patterns' with GPB13–14. This will copy the four selected patterns into the current song position on the SONG page, overwriting what was previously in that position. 'Save & Take over Patterns' does the same, but saves the patterns as well."

Thanks for the info! _b If all configuration options are available in the screen shot at your link, the maker of the emulator chips could probably be asked to make the preferred settings when purchasing the chips from him. Also, if someone has an opinion whether SSU sounds better than SS nano, I'd be interested.

As soon as someone (like @yogi!) has information on how it works with MBSIDv2, please let us know! Is it a 100% drop-in replacement, or does it need setting up etc..? Some guy has written a configuration program for it (on a C64), would it be necessary to use to make adjustments or can you do without it etc..? :-)

Hi, in the user manual's .NGC part, the EVENT_ENC intro section says, "An encoder can send and receive MIDI events. In 'absolute mode' it will handle a value internally, in incremental modes it will just send an inc/dec event and expects the handling of the resulting value at the host site.", However, in the possible enc_modes list, there is no enc_mode=relative, enc_mode=inc_dec or something, which would allow me to send NRPN value increment/decrement commands, instead of absolute values. If EVENT_ENC is type=NRPN, MIOS Studio shows that MBNG is sending the CCs for NRPN selection (98 and 99), and then the absolute value, but is there a way I can send CCs 96/97 for value increment/decrement with NRPNs, instead of absolute values?

Hi, I'm trying out if I can build a controller matrix of 8 encoders and 11 rows of selectable parameters (a bit like Waldorf Blofeld's matrix). Each row has eight parameters, and the 8 encoders at the bottom edit the 8 parameters on the selected row (selection is indicated with an LED). At the moment I have 11 buttons, each selecting a specific bank, and they're in the same radio group. That works as expected. However, I would like to avoid having a separate button for selecting each bank/row, and was thinking whether it's possible to divide the 11 rows into e.g. four groups – rows 1–3, rows 4–6, rows 7–9 and 10–11 – and have one button for each of these groups, with which I could cycle through the rows (i.e. banks & indicator LEDs) in the group (like on the Blofeld, or on the MBSID, for that matter). This way I would need only four buttons to select each bank, still relatively quickly. (With bank increment/drecrement I would need only two buttons, but I would need to press the buttons a lot to select rows that are far apart from each other.) I think this is possible, but the question is, is it possible within just the .NGC file, or does it require something in the .NGR file as well..? EDIT: To clarify further, the point is that only one row/bank should be selected at any time; this is why using several radio groups doesn't work, because one row/group will always be active within each radio group, so with four radio groups, four rows/banks will be active simultaneously.

EDIT (30.10.2016): This post is no longer relevant. Hi, I placed an order at Reichelt.de but forgot to include 6mm D-shaft ("flattened" shaft) encoder knobs. I'd like to avoid paying the extra 9,95€ that Reichelt charges for shipping just a few knobs to Finland, so if someone has at least 8 extra "waldorf knobs" or at least 4 of the Reichelt product linked to below (or something very similar), I'm potentially interested. Ebay is full of cheap and ugly potentiometer knobs with pointers, I don't want those :-) http://www.reichelt.de/KNOPF-10-150E/3/index.html?&ACTION=3&LA=446&ARTICLE=73960&artnr=KNOPF+10-150E&SEARCH=KNOPF+10-150E

MBseqv4+ is a firmware version which will only work on the newer core (STM32F4) because the old one (LPC1769) doesn't have the resources to run it. Basically, all requests for resource-intensive features that are likely to be too much for the LPC1769 based core have just been put into the MBseq4+ basket for some time now (a year or something?). Already some features (like 'undo') have been disabled on the LPC1769 firmware because of the LPC1769 hardware limitations. If your seq is already running on an STM32F4 core, I think you can just update the MBseqv4+ firmware on it (when it comes out).

It's true what k2z3k0 says, SELECT + CLEAR doesn't clear Layer A if it's a Note layer. I tried setting Layer A to Roll, that was cleared without problems, and also other note layers (Layer E etc.) cleared fine.

To clarify: when you record a note, the display jumps into the position where you recorded the note. If you record lots of notes, you won't notice anything strange, because the seq follows the cursor whenever you record a note. This is how I've done it most of the time, so offhand I remembered that recording always follows the cursor position, when in fact it follows the recorded notes. In other words, if you don't record anything for a long time (for more than 16 steps), the running cursor position leaves the screen, and only recording a note will make the seq jump to the recorded position. As to button combination shortcuts, I have cut out small pieces of sticker paper and written "BM" (bookmarks), "FOLLOW" (follow mode), and "TAP" (tap tempo) on them and put them underneath the buttons (SELECT, EXIT, and PLAY, respectively) that work in combination with the MENU button. Also, my selected F1–F4 button functions are marked similarly: REC, JAM (Jam page), TRACK (Track selection), SAVE (Save all). An immediate workaround for quick follow mode on/off would be to assign e.g. a F1–F4 button for it, if you've got one to spare. If you make the workflow page in the wiki (probably better than a forum post), please post a link and I'll write something there on how I do stuff.

I'm not entirely sure what you're asking, because when I record live, the displays follow the cursor position as long as I'm recording. Are you asking about playback and running cursor position? Anyway, MENU + EXIT enables/disables Follow Mode. When the mode is 'on', the displays will follow the running cursor position when the sequencer is running. When the mode is 'on' and the seq is not running, it's not possible to use the datawheel to scroll out of the current display.

Here's a link to my mellotron sample set (zip file, ~200Mb). Let it be said for the record that I downloaded the samples from somewhere on the internet, and my input was just changing them to the right format (the one required by Lee's original firmware), and making the bank.x files. Contents (names from the original files, i.e. not my invention) Bank1: MK II Flute Bank2: Cello Bank3: MK II violins Bank4: Combined choir Bank5: Woodwind 2 Bank6: M300A Bank7: MK II Brass Bank 8: String section Bank1 includes also entries for MBSID drum samples (included in the zip), though they're there just because I set them up, thought they could be improved, but didn't get around to it. The samples are assigned to the lowest keys in the range, with the exception of 0x00 (the first address), because it seems to result in unwanted notes for some reason. [UPDATE: MY DROPBOX ACCOUNT IS NO MORE, SO THE LINK DOESN'T WORK] https://www.dropbox.com/s/6ccbwf84us5lrdk/SP-mellotron.zip?dl=0

Another thing: If Rec is 'on', AStart is 'on', and Fwd is 'off', and you press PLAY, the first step of the active track won't sound.

One little thing I found: On the STEP VIEW page the running cursor position LED changes to a slower mode to accommodate the much denser step display (compared to the EDIT screen). If STEP VIEW button is set to toggle and you exit the STEP VIEW page with the STEP VIEW button, the change from normal and slow running cursor mode works ok. But if you exit the STEP VIEW page with any other button than STEP VIEW, the running cursor mode stays in the slow mode, and won't change until you press STEP VIEW. However, in all cases the STEP VIEW indicator LED does go out when exiting the STEP VIEW page, even if the cursor mode doesn't change.

Tested and working! Ok. I added this in the wiki: "For easily predictable results, the track set as Guide Track should have its divider value set to “16 (normal)” (the default setting) on the track's DIVIDER page. Smaller divider values (i.e. faster tracks) will result in repeating the guiding track wholly or in part, and bigger divider values (i.e. slower tracks) will result in a truncated guiding track." Ok.

The MBSEQv4 beginner's guide is now up on the wiki with some images. I've used EsotericLabs' eps files (based on Wilba's design) for frontpanel overview images, I hope it's ok. In principle the guide is exportable as pdf and printable (there's a button on the right), though at the moment certain "table like things" don't get rendered correctly. I might replace the "tables" with images to take care of the problem. If you want to add sections and correct stuff, go ahead, that's the wiki way :-) The path to the guide from the wiki front page: MIDIbox Projects -> MIDIbox SEQ V4 -> MBSEQv4 Beginner's Guide http://wiki.midibox.org/doku.php?id=mididocs:seq:beginners_guide:start

Here's a few questions that I forgot to pick out from the mass of the text: Random gate trigger layer: is the chance 50/50 or something else? Random value trigger layer: does this randomise all the values in all parameter layers of the step, or just some? Is the random value anything between 0-127, or is the intensity guided somehow? MODE page option 'Sort' for arpeggiator mode: how does it sort the notes? Into an ascending order..? And is the unsorted note order the reverse of the play order, i.e. last played note is "number one" in the arpeggiator track notation?

I tested pre7, AStart with Fwd 'off' works now. However, I also tested Edit Recording mode a bit more, and found (and this is identical to pre5) that while Edit Recording mode does work in Mono/Poly with both SELECT and GP buttons (like I reported back earlier), this happens only when Fwd is 'on'. If Fwd is 'off' and you try to use Edit Recording mode with Poly, only one note gets recorded. Here's also some older stuff that I came up with while writing some parts of the manual that I think were not dealt with yet (if you have them on a list somewhere, my apologies to repeating them needlessy): If divider is doubled (speed halved) for the Guide Track, it will proceed only half-way before forcing pattern change. (See this comment and the next one.) Muting a track cuts off all playing notes on that track, but muting an individual note layer doesn't do the same for the note that's currently playing in that layer -> hanging notes.

I tested some more, and found the first notes of other tracks won't play with AStart when Fwd is 'off'.

One additional note to 4.091 beta: When AStart is 'on', the first played note gets recorded correctly on the active track, but if there are notes in other tracks, the notes in the first steps of those other tracks won't be played.

This is the final section of the draft beginner's user manual: the appendices 1–4 on various topics. No issues came up, so I have no questions. Easy last lesson :-) However, with 4.091 coming out sometime soon, there's already a few details in the appendices that are not up to date for 4.091. I'll publish the text as it is, nevertheless, and update it later for the so-called "final" version. Looking back at the whole manual draft, there was nothing or very little on a number of functions. They can be divided into two groups: 1. Ones I could possibly write about at some point, and add it to the manual later. FX page (only scale mentioned this far) options (only partially covered) TRANSPOSE page (would be easy) MIDI section control metronome BPM (very little mentioned) GROOVE DIRECTION MANUAL MORPH 2. Ones that I'm unlikely to write anything about, now or later, because I don't have the hardware, or otherwise never use USB, DAW, etc. MIDI Ext. ctrl CV configuration ethernet (osc) USB and IIC ports ---------------------------8<-------------------------------------------------- Appendix 1. Customising some button functions --------------------------------------------- Function buttons F1–F4 ---------------------- In the root of the SD card there is a file named MBSEQ_HW.V4. This is the hardware setup file. Most of the settings there don't need changing, and are anyway beyond the scope of this manual. However, on the Wilba frontpanel there are four buttons labelled F1, F2, F3 and F4, which can be customised relatively easily (and are meant to be so). The default functions for the buttons are: F1: Quick access to the Bookmark page F2: Quick access to the Jam page F3: Quick access to Tap tempo F4: Save the complete session In the HW setup file they appear like this: # F1 is located at SR M3 Pin 3 # F2 is located at SR M2 Pin 2 # F3 is located at SR M2 Pin 3 # F4 is located at SR M1 Pin 2 # SR Pin <-- this line begins with a #, so it's "commented out" (not part of the settings) BUTTON_BOOKMARK M3 3 <-- this line defines button F1 as the bookmark page button BUTTON_RECORD M2 2 <-- this line defines button F2 as the Jam page button BUTTON_TAP_TEMPO M2 3 <-- etc. BUTTON_SAVE_ALL M1 2 If you want to change the default functions, all you need to do is keep the "BUTTON_" in the start of the line, add your preferred function after it, and leave the SR and Pin columns unchanged. The possible button functions are listed in HW setup file, and are of the form: # SR Pin BUTTON_STOP M3 5 BUTTON_PAUSE M2 4 BUTTON_PLAY M2 5 BUTTON_MUTE_ALL_TRACKS 0 0 BUTTON_MUTE_TRACK_LAYERS 0 0 BUTTON_MUTE_ALL_TRACKS_AND_LAYERS 0 0 BUTTON_UNMUTE_ALL_TRACKS 0 0 BUTTON_UNMUTE_TRACK_LAYERS 0 0 BUTTON_UNMUTE_ALL_TRACKS_AND_LAYERS 0 0 Lines that have a non-zero entry for the SR and Pin columns are already assigned somewhere (like stop, pause and play above), so there is no need to assign them to another button. However, entries with zeros in the SR and Pin columns (like "mute all tracks" and "unmute all tracks" above) are potential candidates for F1–F4 button functions. For example, if you want to to have a dedicated button for "mute all tracks", you should change one of the F1–F4 button entries to contain "BUTTON_MUTE_ALL_TRACKS". You could replace "BUTTON_BOOKMARK", for example, as bookmarks are easily available with MENU + SELECT as well. It is important to note that if you enable e.g. "mute all tracks" for one of the F1–F4 buttons, *you must "comment out"* the line where "mute all tracks" is set to SR 0 Pin 0. If the "zero address" setting is not "commented out" in the file, it will have the effect of disabling the setting. "Commenting out" is done by placing a # in front of the line, so that BUTTON_MUTE_ALL_TRACKS 0 0 becomes #BUTTON_MUTE_ALL_TRACKS 0 0 Button behaviour (momentary/toggle) ------------------------------------ In the HW setup file it is possible to change the behaviour of a number of buttons, so that they do their function while the button is pressed & held, or the button function is toggled 'on' and 'off' with a single press. For example, momentary pressing & holding the MENU button shows the MENU page only as long as the button is pressed & held, and you have to press another button while pressing & holding the MENU button in order to choose a menu page. If you've set the MENU button to toggle, you can just press MENU once and then press another button to choose a menu (or press MENU again to return to the current page). This allows you to make menu page selections with one hand. This is the relevant section of the HW setup file for configuring button behaviour: ################################################## # Button behaviour # 0: active mode as long as button pressed # 1: pressing button toggles the mode ################################################## BUTTON_BEH_FAST 1 BUTTON_BEH_FAST2 0 BUTTON_BEH_ALL 1 BUTTON_BEH_SOLO 1 BUTTON_BEH_METRONOME 1 BUTTON_BEH_LOOP 1 BUTTON_BEH_FOLLOW 1 BUTTON_BEH_SCRUB 0 BUTTON_BEH_MENU 1 BUTTON_BEH_BOOKMARK 1 BUTTON_BEH_STEP_VIEW 0 BUTTON_BEH_TRG_LAYER 1 BUTTON_BEH_PAR_LAYER 1 BUTTON_BEH_TRACK_SEL 0 BUTTON_BEH_TEMPO_PRESET 0 Appendix 2. Bookmarks --------------------- The Bookmarks menu is available in the main menu (press EXIT once or a few times, depending on where you are), or by pressing MENU + SELECT. Bookmarks allow you to store frequently used pages and settings to be recalled at the push of a button. There are two kinds of bookmarks: global and local (session dependent) bookmarks, eight each. In the Bookmarks menu the global bookmarks are available in the left LCD, and the local ones in the right LCD. Global bookmarks are available in all sessions, while local bookmarks are particular to each session. However, it is possible to copy local bookmarks across sessions in the Sessions Import/Export menu (UTILITY -> Disk -> Sessions Import). Choose the source session in the right LCD and turn GPK9 to select 'Bookmarks' as the imported type. Pressing 'IMPORT' will replace the current session's local bookmarks with the imported ones. A bookmark can be recalled by going to the Bookmark page and pressing a button to select the bookmark you want. A bookmark can be stored by going to the Bookmarks page and pressing & holding a GP button for 3 seconds. The page that was selected before entering the Bookmarks page is stored, along with a number of settings. (See the example below.) Bookmark names can be changed only by editing the global or local bookmark files, both called MBSEQ_BM.V4. The maximum length for a name is five characters. If you absolutely must have more than five characters for the name, you could save the same bookmark on two adjacent slots and edit their names in the bookmark file so that the one on the left in the pair has five characters and the one the the right has up to four characters. The global bookmarks file is at the root of the SD card, and the local ones are in the same folder as the session which the bookmarks belong to. Besides the bookmark name, it is possible to edit also the other bookmark parameters by hand in the bookmark files. The example below also lists the settings which are stored in a bookmark. #################### Slot 1 <- slot name, do not edit! Slots 1-8 = global bookmarks, 9-16 local bookmarks Name Def. <- replace "Def." for custom bookmark name (max. five characters) #################### +Page EDIT <- name of selected page +Group 1 <- selected group number, 1–4 +Tracks 1000000000000000 <- selected tracks, 1 = track selected, 0 = track not selected +Mutes 0000000000000000 <- selected mutes, 1 = track muted, 0 = track not muted +ParLayer A <- selected parameter layer, A-P +TrgLayer A <- selected trigger layer, A-G +Instrument 1 <- selected instrument (useful only for drum tracks)*** +StepView 1 <- Step View mode on or off +Step 1 <- selected step (cursor position) +EditView 0 <- Edit view mode, 0 = step view, 1 = layer view, 2 = trigger view, 3 = 303 view +Solo 0 <- solo button mode on or off +All 0 <- ALL button mode on or off +Fast 0 <- FAST button mode on or off +Metronome 0 <- metronome on or off +LoopMode 0 <- loop mode on of off +FollowMode 0 <- follow mode on or off The plus or minus sign in the beginning of each line can be used to prevent the setting from being overwritten by a bookmark, when you store it on the bookmark page. Plus allows overwriting, minus prevents it. For example, the line -Tracks 1111000000000000 would mean that if you save a bookmark in the same location, the track selection won't be stored, but it will always be what's written in the bookmark file – in this case, this bookmark will always select tracks 1–4, no matter what the track selection status happens to be at the moment you save the bookmark in this slot. Appendix 3. The MIDI Router --------------------------- You can access the MIDI Router page from the main menu, or with MENU + MIDI -> MIDI Router (GPB5–6). The MIDI Router allows you to route incoming MIDI messages from any of the input ports to any of the output ports. *It is independent from the other MIDI settings of the sequencer*, and in some instances you have to pay attention so as not to have parallel in/out settings – this can lead to e.g. notes getting forwarded twice. The router has a maximum 16 nodes, each of which governs the routing from *one input port to one output port*, with further optional channel limitations. All the nodes are in effect simultaneously. On the input side, GPK9 selects the node to be edited, GPK10 selects the physical input port on which the messages are coming in, and GPK11 selects the MIDI channel that is allowed through. The channel setting (GPK11) can be: a) 1 to 16, for allowing messages on single MIDI channel; b) 'All' for allowing messages on all channels; or c) '---', which effectively disables the node, as no MIDI channel is allowed through. On the output side, GPK12 selects the output port where the node's input port's MIDI messages are routed to. GPK13 selects the MIDI channel which the outgoing message is sent on. The outgoing channel doesn't have to be the same as the original incoming channel, so you can e.g. transform incoming channel 1 to outgoing channel 13. Channel options are: a) 1 to 16 for a single MIDI channel. All incoming MIDI messages, regardless of their original channel, are sent out on this channel; b) 'All' for sending the message on its original channel; or c) two special options: Track and Selected Track (Sel.Trk). If the output port/channel option is 'Track', the router will direct the incoming messages to the track whose *ordinal number* matches the incoming MIDI channel (provided that the input port/channel options allow the message through). For example, if you have a MIDI controller that's sending MIDI data on channel 7, 'Track' option will send the message out on the port and MIDI channel set on track 7's (G2T3) EVENT page. MIDI channel 10 will get sent out on track 10 (G3T2), etc. If the output channel option is 'Sel.Trk' (Selected Track), the router will direct the incoming messages to the sequencer track that is *currently active* (provided that the input port/channel options allow the message through). If you have several tracks selected, the MIDI message will go out on the channel with the lowest ordinal number (track 1 before track 2, track 5 before track 6 etc.) The final option on the MIDI Router page is DefaultPort. The tracks' EVENT page and a few other pages allow you to select 'Def.' as one of the Port options. If you select 'Def.' as the Port, it will refer to the Default Port setting on the MIDI Router page. Note that the router settings might overlap with the Jam page note live forwarding option ('Fwd'). If you have Fwd 'on', it will forward incoming MIDI messages on the 'Jam' bus (see section 4.1.1.) to the active track's output port, set on the track's EVENT page. This is done regardless of any MIDI Router settings. However, if Fwd is 'on', and at the same time you have a MIDI Router node routing MIDI messages to the same port and channel as Fwd is forwarding them, MIDI messages like notes will get triggered twice, almost simultaneously. This most likely alters how the note will sound, and perhaps causes hanging notes. If you are using the MIDI Router to forward MIDI messages from one or several MIDI controllers to output ports, you might want to make sure that Fwd on the Jam page is 'off'. On the other hand, note that the Live Patterns function depends on Fwd being on. (See section 4.1.5.) Example: If you have two MIDI keyboards, one in IN1 (a plain MIDI controller) and the other in IN2 (a keyboard synthesizer that's sending on, and listening to, channel 1), you could set them up so that one of them always plays the channel it is set to send on, and the other always plays the currently selected (active) sequencer track. Let's say you want to set your keyboard synth to play the active track (selectable on the group and track selection buttons on the sequencer), and the plain MIDI controller to play the channel you've selected on the controller. For this to work optimally, you need to turn the Jam page Fwd option 'off' to avoid forwarding messages twice. Also, you want to set your keyboard synthesizer's 'local' function off, so that the synth is triggered only via MIDI. On the MIDI Router page, set Node 1 like this for the plain MIDI controller: IN Chn./P OUT Chn./P Node 1 IN1 All OUT1 All This lets through all messages coming in at IN1 on all channels, and directs them to OUT1 on the same channel it came in on. In other words, if the incoming message at IN1 is on channel 11, it is forwarded to OUT1 on channel 11. This setup is very useful if you have a multitimbral synthesizer that can be played on several MIDI channels, or you have several synths connected to OUT1, either with MIDI Thru boxes or by daisy-chaining equipment with their MIDI Thru (soft or hard) ports. However, if you're using only one synth in each output port, you can make a dedicated node for each output port: IN Chn./P OUT Chn./P Node 2 IN1 All OUT1 All Node 3 IN1 All OUT2 All Node 4 IN1 All OUT3 All Node 5 IN1 All OUT4 All With these settings, everything coming in on IN1 will be routed simultaneously to output ports OUT1–4. This way you can control the synths at each output port with a single MIDI controller at IN1, just by changing the sending channel on the MIDI controller. Node 2, for the keyboard synthesizer, is set up like this: IN Chn./P OUT Chn./P Node 2 IN2 #1 Sel.Trk Node 2 contains the settings for the keyboard synthesizer, which is connected to IN1, and set to send on, and listen to, exclusively channel 1. This way you can use the keyboard synth to play itself via the sequencer (remember to turn the synth's 'local' setting 'off'), but also any other synth that you have connected to the sequencer, just by using the group and track selection buttons to select the right track on the sequencer. Appendix 4. MBSEQv4 CC implementation ------------------------------------- The following is a simplified list of what a track's configuration consists of. The full information can be found below. – FX settings – MODE settings – TRANSPOSE settings – DIRECTION settings – DIVIDER settings – Loop points – LENGTH – GROOVE styles – MORPH settings [list of MBSEQv4 CC implementation follows]