u-link

Well, you are welcome, it's pretty cool to be able to get my wishlist features integrated into this awesome machine! I reckon as a workaround, I could just send from the Mixer Map out of a physical MIDI out and then via a cable send that back into an input that I designate as the control input. I think I read somewhere on the forum that somebody did something similar by directly wiring one out to one in on the LPC17-core (but I think it was for a different purpose, can't recall). Yes, of course, that is what I meant. It would be great to be able to control those FX parameters via MIDI, and also the parameters for the LFO. I realized the linked CC implementation file has last been updated October 2009. Is there an updated and expanded version or has CC implementation halted?

Reconsidering my statement above, i assume it should be possible to use the four assignable Cs in the mixer map via a loopback Bus to control sequencer parameters via the CC implementation. That would be great, as it would be a way to work around a design limitation, this being that you are only ever able to modify parameters of one track (or the same parameter of several tracks, if several tracks are selected, but then not individually – another workaround is to stay on the same page, FX Delay in that case, and change the active track via the lefthand buttons). It's a bit like on the Machinedrum: I can only change the decay of the BD if I'm on the BD channel, not the HH decay. Whereas on the Tr-909, I have a knob for those parameters constantly in front of me, and I can shorten both the decay of the BD and the HH at the same time. The Machinedrum tries to clumsily work around this by giving you the option of sacrificing a percussion channel for a "control machine" (I think that is what they are called, it's been a long time since I got rid of that ...), which is some kind of macro, and you can set six parameters from different channels to be controlled off one page (eg the decay for the BD, the HH and the Snare tune etc). It would be really elegant to repurpose the Mixer page to get this feature, but I simply can't get that to work. (My example wouldn't work anyways cause the CC implementation doesn't list Delay Feedback as a controllable parameter. I am not sure if this is because it is really not available or the CC Implementation file hasn't been updated?). But what should work is to set the Clock Divider (CC044) via a Mixer Enc: In the MIDI menu, select Ext. Ctrl: In: Bus1; Out: ---; Chn: ---, then in the MIXER menu, select Enc 1 to send on Bus1, press the Select key, set Enc1 to CC044. But this doesn't work! What am I doing wrong? Somebody please do enlighten me!

It's too bad that those faders (OPT Menu item 14) are an option only together with the ever so slightly scarce BLM16x16+X. It would be great if one could simply connect a cheapo (... or DIY'ed, of course) MIDI-Controller that would then turn into this "meta-controller", eg controlling the values for each track's saved Mixer Map CCs (that might be assigned to a different CC-number in each map, and a pass-thru mode would make sure there is no value-jumping). Or, even better, they might be assigned to control FX parameters, like the MIDI Delay feedback for eight channels at the same time ... Imagine having a motor-fader controller for that! Sick performance possibilities would ensue!

I already feel the untra-tight Chi-town-boogie shuffle pouring out of my synced devices ...

Please add me to the list, too! Thanks a lot!

Please put me on the waiting list for a case and a PCB, too.

Would it be possible to have the DIN Sync clock and the MIDI clock out follow internal shuffle settings? That would be amazing for locking external machines with built in sequencers that are just being clocked by the MBSEQ into the same groove: just write all the patterns with no shuffle, and let the clock be shuffled exactly the same as the notes being spit out. While we are at it, Clock divider for the MIDI clock being output (even better for each out separately) would be great, too!

Personnally I would find it useful if the Parameter Layers would be nameable in a similar way to how the Drum Notes are. Like this, you could create a Preset for a certain instrument, assign Parameter Layer 5 to say CC 074, save as preset and be done with remembering that this is the cutoff controller on your synth. Maybe it would be even be possible to create a list / table in a text editor with a config file containing info about which instrument is connected to which MIDI I/O (like the MIDI Setup on OSX). Onw were to be able to store several such configurations, eg one for the studio, one for live sessions etc. Further, this idea could be extended to include a CC implementation table for each instrument. You could then, instead of selecting ports / channels, select the synth directly, and configure the tracks with the modulation destination being referred to by name. I guess most people using hardware synths only have a limited amount of instruments, so taking the effort once to list all the I/O and CC parameters would be worthwile (and the lists could be shared via the forum). Finally, it might be possible to have an integrated converter to MIDI Sysex, so you could directly control synths that only have a Sysex implementation, similar to the standalone app that julienvoirin developed in this thread: midibox.org/forums/topic/16302-roland-juno-106-and-alpha-juno-2-sysex-translator/#comment-149077 That might make it feasible to control parameters from the Mixer Map on a Sysex-only synth and automate them via Parameter Layers!

Pre6 seems to solve the issue.

Might I suggest the possibility to shuffle the MIDI / DIN Sync clock that is being output, too? This is a feature that is getting more and more popular on the new breed of "Sync-Box-Modules" à la Innerclock Systems Sync Lock. Imagine you run an 808 slaved to the Seq via Sync24. Normally, the 808 doesn't have shuffle, but, if one were to shuffle the clock the same as the internal tracks, it would follow the groove perfectly. There is a lot more old-school drum machines that don't feature shuffle (Casio RZ-1 eg). For live jams, it would also be extremely convenient to make sure everythng follows the same groove, as you you could resort to creating all your patterns without shuffle on your synced machines. Personnally I only partly agree, I think it can sound great to have some shuffled tracks running against straight ones, for example on hats, or the bass line. it gets tricky if you overlay sampled audio loops from different records that all have differing amounts of shuffle, though. I hate having to insert warp markers in a clip in Ableton on almost every distinguishable 16th note, in the end I think it pretty much kills the original groove, which is why you sampled something in the first place. So I stopped doing that kinda stuff pretty much and use hardware samplers, you just adjust by ear, end up doing simpler stuff, which is often more effective!

I won't be able to do try this before next week , as I am going abroad tomorrow til Sunday. It is in fact an LPC17-core in my case.

Hi Thorsten, many thanks for the detailed answer, didn't know about the Select-behaviour. Muting Trigger Layers via CC would be exactly what I am after, I think, as you could map them to some kind of pad controller.

I upgraded to this, too, and since then all I get is "Hard Fault at PC=0x00048f30". Sadly in my case, it doesn't go away with a reboot. I intend to try and set the jumper on the core to "enforce bootloader mode at start up", as I can't access the Core over MIOS Studio, and try to upload the older Software version again.

Hi, I recently finished building my Sequencer. To my big surprise, everything worked immediately, and I am really happy with it so far. I am still learning how to use it, so my question is in regard of its simplest mode, the drum track. Is it possible to mute individual drum lines / notes in a drum track via MIDI? If so, how would I go about doing that? As is, it is not possible to eg mute the kick at the same time as the bassline (which would be on another track). If that would be possible, I could assign buttons on a MIDI controller to control their mute status. As a feature suggestion, maybe it would be possible to add a way of handling mutes like on the Elektron Machinedrum, where, if memory serves me correct, you can hold down either the shift or the mute key, select which sounds to mute / unmute, the action only being performed the moment you release the shift / mute key. Even better if you could do that for individual drum lines and full tracks. Also, I am a bit suprised about the "Clear" feature in the Rhythm tracks. It clears the whole patterns, while I think it would be way more useful if it: a) would just clear that one drum line (maybe with a double-tap?) b) would clear the notes in that one drum line while being depressed (as on the TR-909 when in Step Write mode) c) would bring up the same screen as when pressing Mute, so you can select which lines to clear (preferrably for the duration of the knob press) – as on the TR-909 in Tap Write mode. Looking forward to some input of more experienced users!

That might be the easiest idea. I also thought about using a "Wiring" board, which I guess you could program to do the triggering (well, not me, but a friend of mine who knows programming). At least for making an expander. The much cooler thing would obviously be a complete MB-909 thingie with integrated sequencer... But you are applying the rim trigger to a point AFTER IC1/10, right? Please post anything new you find out here, that would be much appreciated!

no, I don't, the only thing I have is the voice board. Except for my intact 909, which I have no intention of slaughtering - it might get sold if this ever gets to work, though. The 909 service manuial also states that the trigger signal on the 909 is 2 ms in length, can that be changed? Thinking more about it, using two separate drum-channels on the Seq might not be the best idea, as you don't see which steps are on at one glance - thought about that as I mainly use the 909 in Tap mode, not Step programming. I think it would be easiest to just connect the trigger of the Dout directly to the input of the sounds, after the IC1/10, right? So if you only send a trigger signal to the trigger input, without triggering the accent, there is no signal output? Regards, Gabriel

Hi,I've been lurking around here for quite a while. I actually have a spare 909 voice board, too (which I haven't tested yet, but it is new, purchased some years back when Roland still had them on stock by a friend), and had the same idea. I was thinking that on the v4 seq, with its sixteen drumtracks (or the dedicated MB808 seq), it might maybe be possible to use two tracks for the 909 sounds that support accent, one for the unaccented, one for the accented (quite like this is handled on the real 909), implementing it so that when the MIDI-interface on the 909 receives the second note, it also triggers the accent circuit on the 909 board.