Since 1.7.3 just came out and it has MIDI Import.... I really hope that can lead to a future release including MIDI export like jayneural mentioned in his post 
-
-
I thought the same thing, maybe some hope for at least individual clip SEQ or SONG export soon
Even individual SEQ export would be nice as it would allow us to save/transfer snippets of sequences to other projects, or create/maintain our database of MIDI clips as I already tend to do on Ableton (yes I know the BB is not Ableton... but...)
-
-
+1; more pads is almost essential; and adding pages is a quick way to solve the issue (assuming memory is large enough to do so, or there is a way to write on SD card sequence pages altogether, so you can have unlimited sequences).
Also would be useful to not have a sequence with all 16 channels/pad in it; sometimes you want just a variation on a specific channel/pad, so you end up copying a whole sequence to change just one pad/channel; which is a waste. Having separate lanes for sequences, where you can select which pads/channel you want to have in it, would be really nice (and the ability to mute/unmute channels via automation, and midi export would be a great companion to make an even better sequencer experience).Comment
-
the workarounds here are seemingly focused on providing a way of increasing the sequencer horsepower during the building of a planned arrangement; I think where I & others would benefit is in having more sequencers available (pages of them, or by scrolling) for live improvisations. more permutations of the same stuff, in other words. I don't know what direction the song's going to go in, from one performance to the next, so.... options.
at the moment, I've been sequencing multiple pads in each sequence, but ideally the main sequencer page would offer a 'drill-down' where the top layer is pages of sequences mapped directly to the corresponding pads; then you'd select the pad's page of sequences & there are sixteen sequence locations underneath, all tied to that pad.
from this page, using the same idea of a grid in each top corner, you could quickly navigate to another pad's sequencer page (top left), or to another sequence in the same page (top right).
in the text at the top of the other views (where it says "seq 1" & so on now), this would change depending what pad is selected, to show you which of that pad's sequences you're hearing/about to record into.
the song/section editing gets complicated, though- you wouldn't be able (easily) to assemble a section simply by arming & disarming the sequences as they play, because selecting them would be a two-stage process.
ideas?Comment
-
+1 Hell yes! Please for the love of delia Derbyshire make this possible!Comment
-
Wouldn't more sequences overload the processor? When loading some presets and activating all 16 sequences my bb starts to turn into clicking concerto. Just got mine a few days ago, so maybe I'm missing out on something.Comment
-
I think your head is in the right place here. With the current 16 seqs, it’s a crap shoot as to how many of them will play in a given preset without strain.
If more sequences are added, it invites a user to activate more than 16 seqs simultaneously, which will likely strain the blackbox.
The argument could be made that: “since 16 is already sometimes a strain, why not add more? “
I’m not making that argument, just recognizing it might exist.
-
-
I see a different way it could be done, than adding just another grid of 16 pads or re-arranging/resizing the grid.
It could be by adding a "drum kit" type of pad which would be nothing more than a page of UI that would let you select multiple samples for your drum kits. It would then work a bit like a multi-sample type of pad.
For each sample you would also select a "type of drum" field which will provide "Kick, snare, HH, other..." predefined labels. So then these labels will show-up on the SEQ screen when working on a drum kit type pad.
That would let you group all your drums into one pad and have the other 15 for other instruments, FX, vocals.
The MC-101 works a bit like that where "Drum tracks" can hold a full sample kit.Comment
-
Personally, as a non-user of the specific drum sequences use case, I find the more generic solution of adding a second page with 16 seqs pads more practical - overloading the seqs hard button to toggle between both pages would be simple enough.
Though a way to assign optional seqs names and then to toggle between seqs names and mini steps preview would be a great addition for keeping seqs organised.
-
-
hi,
so i finally did the 174 update. i did not notice anything going wrong with this update. but there is still no possibility to filter midi channel to be rec. i'm really disappointed, i'm using the BB as drum expander, and then i can't play and record leads pads while the drums are triggered from external gear... neither with the touchscreen, nor some midi keyboard. very frustrating.Comment
-
+1 This would be awesome. Same for MIDI import. It's a bit clunky to import all channels when only one is needed.Comment
-
If add more sequences for samples is a concern re. processing power etc. Then maybe add an additional 16 that can only be used for external midi. If you limited the first 16 to internal samples and the second to external midi only, that would also clarify the whole issue of needing an empty pad to sequence external midi thing, and free up pads.
I really want the BB to be the brain of my setup, and this would make that possible.
ThoughtsComment
-
This is a duplicate, consider merging it with the other thread on this subject!Comment
-
hi all,
i'm still a little disapointed about the fact that this midi in channel rec selection, (as said by the thread owner, heiningair) is still not possible. disapointed because 1010 is pretty good when midi is involved, whereas this midi channel rec selection seems to me to be a basic midi function...
bComment
-
Lots of really basic MIDI functionality missing! Definitely wouldn’t call this any sort of full fledged MIDI sequencer yet. +1 to this, unbelievable really. Architecture needs workComment
-
The processing power is not involved in having more sequences.
You can only have one sequence playing at time; you can chain as many sequences as you want; but they do not play concurrently; unless I am missing something. Why would you play multiple sequences at the same time? Maybe I used the Blackbox in the wrong way all this time?
My original post is to have more than 16 sequences, as clearly stated; so why are we talking about more than 16 pads and more samples playing concurrently?
Also with other sequencers; you are limited by the amount of midi data, not by the amount of samples; if you use the Blackbox as sequencer, you should be concerned mostly about the number of midi events that run concurrently, which is what should affect the CPU. Or am I missing something?Comment
-
some example use cases:
* split your sequences by function (rhythm section, lead, vocals, pads, etc.) rather than by song section,
* split the rhythm section into components: bass, hihats, kick drum and snare, so that you can create variety in the rhythm section and/or mix them separately. Eg you would want your kick drum and bass line to have the same punch.
Obviously, you are right about the processing limit due to polyphony. There are things one cannot change about the blackbox. I do not think that users want to play 32 seqs at the same time, rather than to have more variety in the sequences. -
Okay pallozza. Allow me to explain what I mean in a little more detail. At the moment each sequence has to be associated with a Pad, so if you want to sequence an external midi synth you effectively loose the use of one of the 16 pads. What you are asking for if more sequences, so without any other changes to the why things work at present, I was presuming that would also require another 16 pads, which would by default be fully functional sample pads.
My suggestion was to leave the current configuration or sequences to pad the same, but add an additional 16 sequences dedicated only to external midi. My presumption (which I admit may be wrong) is that the cpu cost of a sequencing and playing back samples would be greater than for just sequencing external midi alone.
So if more than 16 pads/sequencer tracks isn't possible, maybe my suggestion is more achievable.
Can anyone explain the Pads to Sequences relationship better than me.... because it's this that is at the centre of my point really and I'm not doing a good job of explaining it. An I right that is you sequence external gear you loose the use of a pad? -
Thanks for the clarification neilstapleton. I get your comment now.
From my perspective; a sequence is a set of instructions for each of my synths; since each pad is a synth for me (or a channel for a multi-timbral synth, in the case of a synth with 16 channels), I favor having more sequences, since I can create more variations. If I lose pads, that is OK; I understand the limitations of the device, and 16 pads is OK for me.
I like your idea of adding more sequences for midi only; but that would double the CPU load though; since you have not only the 16 pads for midi but the 16 pads for [whatever you may add in it]; and in that case I agree that it would be heavy on the system.From my perspective I wish the Blackbox was more like the Pyramid or the Deluge; with a sequencer that would allow you to get some serious power as far as number of tracks and length of patterns. For 100 dollars more you can get a MPC One which in terms of features and sequencer capabilities, is quite a step up, at the cost of losing portability and ease of use.
And Georges I am aware that the sequences do play simultaneously; I just don't use the BB in that way You have just 16 sequences; if you start to add an instrument or 2 per sequence; you end up with very limited number of variations, and that is crippling for me (pretty sure others thrive with deprivation and being forced to use limited resources; I am just not like that, and what I make is rubbish if I work in such conditions 
)
-
-
just for a differing opinion, if it's a CPU resource allocation issue between adding more sequences versus having the UI reflect midi input on assignable parameters or other things "missing" (I use this term VERY loosely) I'd prefer the original 16 be fully bolstered. There is SO much variation to be made within each sequence already, especially with the new probability and off-grid options. I have yet to have a scenario where I needed more than the 16 available personally, but I can absolutely understand how more could be utilized.
Every device available has limitations, which get defined by all sorts of reasons/causes. BlackBox to me has always felt like the workflow revolves around that 16 position "launcher", both of sequences and pads. Adding another page or pages of these would dilute that workflow, and if the added tracks of sequencing are at the expense of fleshing out the existing environment, it just doesn't feel worth it.Comment
-
The constrains depends from the style of music. For most beat making; 8-16 patterns are plenty; but if you work on other genres, you will end up having more variations, especially if you use different instruments (some of my compositions have 40-50 instruments easily, and that's not even fully orchestrated). I could see a step forward if there is a way to automate pads mute; so at that point I don't see a sequence as one block that contains all my instruments that I want to play at that time, but I have the ability to design each sequence with the feature of being able to mute and unmute pads while the pattern runs; which is equivalent to make X sequences for the variations
As far as workflow; does it bother you to have extra pages that you can ignore? If you are OK with 16 pages you will never know that there are more; so I don't really see a problem with the workflow. Unless you are forced to see all the extra sequences (which won't happen on such small screen), you can continue to work as now, and not even think about diluting your workflow.Comment
Comment