borfo

Actually, it looks like FX-Duplicate could be used to do this... Set up a track on BUS1, then use FX Dup. to duplicate the track to a MIDI out port. I haven't tested this, but it looks like it should work.

TK - a question for you or anyone else who would know (for example, anyone who's slightly less lazy than me and feels like doing a simple experiment to test this rather than bothering TK about it)... When MENU+COPY is pressed, the currently selected tracks are saved as COPY1.V4T, COPY2.V4T, COPY3.V4T, etc. If you had previously saved 6 tracks (so: COPY1.V4T, ... COPY6.V4T exist on the SD card), and then you save two tracks (COPY1.V4T and COPY2.V4T), what happens to COPY3.V4T ... COPY6.V4T on the card? Are they deleted? I'm assuming they wouldn't still be pasted in when the user presses MENU+PASTE, correct?

This is the discussion thread for the MIDIdocs article "Utility Functions" in the Wiki. Feel free to ask questions or make comments or corrections on the article in this thread.

This article is still a work in progress at this point - I'll add some photos and graphics to help illustrate which buttons do what, and what the different views look like at some point. Feel free to add to the article if you want to. edit: added some crappy images.

This is the discussion thread for the MIDIdocs article "Using the BLM" in the Wiki. Feel free to ask questions or make comments or corrections on the article in this thread.

I'm just writing up some "using the BLM" documentation. I guess 303 view isn't accessible on the 16x8 novation blm? Not an issue - it's probably not too useful with only 8 vertical buttons anyway, just checking for documentation purposes. ...and it would be accessible with 4 launchpads in 16x16 configuration? Also, what's going on with the very bottom row of the BLM when you're in grid mode, and you select the lowest octave with ALT+Octave Button 8? It looks like the bottom row of notes indicates which steps in the sequence have active notes, but you can toggle it on, but not off... Does that bottom row represent the Gate trigger layer?

ALT+Pattern save and the drum instrument selection are tested and working great over here.

...Testing this a little more: Are drum tracks fully implemented yet in grid view? Are only the first 8 drum instruments accessible, or am I just not realizing how to toggle to the other 8 drum instruments? Assuming the toggle between instruments isn't implemented yet, what do you think would work best for toggling between drum instruments 1-8 and 9-16? I guess the ALT button wouldn't conflict with anything here - when ALT is off,drum instruments 1-8 could be displayed, and when it's on, 9-16 could be shown. OR, to follow the ALT octave selection model for note tracks: when ALT is on, the buttons on the left side could toggle between drums 1-8 and 9-16. The left buttons could light like the top buttons do when a track is shorter than 256 steps... Left buttons 1-4 could light for Drum Instruments 1-8, and left buttons 5-8 could light for Instruments 9-16.

Yet another gamechanging set of improvements... Thanks yet again. You even added the pattern quicksave and track view/trigger layer things... Awesome. Everything's working great on my end. If it's easy to implement at some point, maybe the pattern quicksave should require ALT to be held down - that way there would be less chance of accidentally saving over a pattern when you meant to launch it.

haha... three years later...

Cool. They're yours if you want them. On October third I'm leaving on a sailing trip for a month, so it'd be easiest for me if it could get done sooner rather than later. If you're sure you want them, just PM me your address and I'll mail them out, and you can paypal me the cash whenever you get around to it.

This is the discussion thread for the SEQ V4 MIDIdocs article "Configuring Tracks" in the Wiki. Feel free to ask questions or make comments or corrections on the article in this thread.

This is the discussion thread for the SEQ V4 MIDIdocs article "The MBSEQ_HW.V4 File" in the Wiki. Feel free to ask questions or make comments or corrections on the article in this thread.

My use case for 3 would be sending patch sysexes to Shruthi synths. But the SEQ can't record sysexes anyway, and you're probably right that people wouldn't bother organizing sysexes for that. Just throwing the idea out there.

No special use case for the ramp in the mixer map page, just wanted to make sure I get the documentation right.

I've just skimmed through this thread and saw a lot of discussion about price, but I must have missed the post(s) that actually set out the price for the RTP-Midi board... Are these still available? how much are they? Are you selling that custom Core board?

More on the CC control of Mixer Maps question. I misread your question and probably answered a bit too hastily. This is a bit of a guess since I haven't tried it yet, but I imagine that because there are 127 Mixer Maps available, the value sent on the external control CC# will determine which mixer map is dumped. ie: if you've got CC 111 set for Mixer Map dumps, and you send a CC 111 value of 3, I imagine Mixer Map #3 will be dumped. Maybe someone who uses external control can confirm this. Also, in your example, if you're using a track on the SEQ (rather than an external MIDI controller) to send the CCs that trigger the mixer map dumps, I think you would have to send that track to Bus1-4, and set up that bus on the MIDI External Control page for the mixer map trigger CC.

Thanks. v. 87 is a prerelease that supports novation launchpad BLMs - it's what I have installed right now, and I figure it'll be released soon enough, so may as well use it - that way the article will stay up-to-date just that little bit longer. haha. I've never triggered a mixer map dump from a CC, so I'm honestly not sure... But that sounds right. I am planning on writing an external control article in the future, and when I do that, I'll test out all the external control features, and I'll add some more specific examples. In the meantime, feel free to test it yourself and add an example to the Wiki. I'm relatively new to the SEQ, I am finding that writing these articles is a really great way to get to know all the features. Added. Thanks.

DUMPING JUST ONE COLUMN OF VALUES WITH GP BUTTONS I think it would be useful in Mixer Maps to be able to trigger a dump of just one column of MIDI map messages by pressing one of the GP Buttons - instead of sending all 16 sets of values as you do with a full Mixer Map dump, it would be useful to be able to send just one set of values (ie: just the Prog Change, Volume, Pan, CCs, etc. controlled by one of the 16 encoders). This would expand the possible uses of mixer maps quite a bit, I think. For example, you could use the 16 columns of information in one Mixer Map to trigger 16 different states of one synth (different patches, volumes, CC settings, etc. in each of the 16 columns, but each column would be set to the same port/channel), and you could press the GP buttons to manually switch one synth into different states as you're playing back a pattern. You could load a different Mixer Map to trigger 16 states on a different synth in the same way. ...and maybe holding FAST + pressing one of the GP buttons could send only the single message that is currently displayed above that button, rather than the whole column or the whole map. DON'T SEND MIDI ON ENCODER TURN OPTION Currently, whenever you turn an encoder to adjust one of the Mixer Map settings, the MIDI message you're adjusting is sent. I think it would be useful to have the option to disable this - so that you could adjust the values in a Mixer Map without sending the message to your synths until you trigger a dump of the Map (or the column, if the feature I described above is implemented at some point.) To implement this, a "LiveSend/NoSend" option could be added to the Mixer Utility Functions page that is shown when you hold SELECT in Mixer Map mode. SEND A SYSEX I haven't really tried working with Sysexes on my SEQ yet, mainly because there are so many other features to explore on this device and I haven't gotten around to sysexes yet. But I think it would be useful if in addition to the 12 Mixer Map settings (volume, pan, CCs, etc.) for each of the 16 columns, you could also attach a sysex file (ie: point to a syx file in the /SYSEX directory) to each column that would be sent along with the Mixer Map dump. You could use this to send patches to synths on a pattern change, for example. ##################### Again, none of these are particularly important or urgent, I just thought they'd be useful features to consider adding at some point, or not.

The "sync mute/unmute to measure" function is great. Here's a small change that would make it easier to toggle the feature on and off: Currently you have to go into the options menu to enable or disable syncing to measure. While playing around with this feature, I found that I wanted to be able to sometimes sync mutes to measure, but sometimes immediately mute or unmute. I don't think there is currently a way to do this other than going into the options menu. Since the SELECT button is already used for selecting a group of tracks to simultaneously mute or unmute, I thought the FAST button could be used to quickly and easily enable and disable syncing to measure. It could be implemented in either of two ways: 1: Hold FAST then press GP buttons to instantly mute/unmute tracks, regardless of whether Sync to measure is enabled; or 2: When FAST is active, Muting and unmuting is synced to measure. When FAST is inactive, muting and unmuting happens immediately. (or maybe the other way around is more intuitive, actually: FAST=instant) I prefer option 2. (edit: actually, I'm not sure that I do... Both ways have their advantages.) This isn't a particularly important feature to add or anything, it just occurred to me while I was working on documenting the MUTE and SOLO functions, and I thought I'd write it down here before I forgot about it.

This is the discussion thread for the SEQ V4 MIDIdocs article "MUTE and SOLO" in the Wiki. Feel free to ask questions or make comments or corrections on the article in this thread.

This is the discussion thread for the SEQ V4 MIDIdocs article "The ALL Button and the FAST Button" in the Wiki. Feel free to ask questions or make comments or corrections on the article in this thread.

In previous versions, you could press and hold the ALL button and change the Step Selection Mask (the set of steps that will be affected by the ALL button) with the GP Buttons. This worked on the Edit Page, and in Mixer Maps, for example. At least, I think it did... I suppose it's possible I'm misremembering... In firmware v87 it seems this functionality is broken - you have to go into Edit > Step Selection View to change it now. Is this intentional? Maybe due to a conflict with the step recording feature? Also, on the Mixer Map page, the ALL button doesn't create a ramp if an unselected step is moved... Is that intentional? I'm asking these nitpicky questions mainly because I'm writing some documentation on the ALL and FAST buttons and want to make sure I'm documenting the right features, not so much because I care too much about either of the above features. Holding ALL to select the stepmask is a nice feature though.

I emailed him a while ago about CS boards. He's out of stock right now, he's expecting new stock to arrive sometime soon, they'll be back in the store eventually, if nobody on the forums has one they'd sell you in the meantime.

Here's TK's last post re: BLM features from that thread.