Amaury wrote:Hi Forge,
Don't do it if it hurts!
that's a nice theory, but how can I not? I'm trying to use Live 7, I've gone past the point of no return on most sets, but i still come across as many problems as I did during the testing - so I either ignore it, or I tell you in the hope it gets fixed!
as it stands there are a few I work around daily and havent got around to reporting
Amaury wrote:
In your case: dropping a sample into the chain list of any drum rack will always set the newly created chain to a unique mapping (a note, and not "ALL"). Remember, then, that a pad does not represent a chain, nor a device, but a note, only. If you want to layer a sound with an existing sound (be it a single hit or already a rack), ALT drag it onto the pad you want it on. It's far easier to work with pads only.
No I'm pretty sure the things I'm reporting are bugs - these are not to do with working with drum racks, they are weird behaviours that make no sense
I fully get the bit about pads being shortcuts etc now
at least the one up the page with the screenshots - it's too unpredictable to be intentional, unless you're all drinking Stefan's weird halucinogenic tea now
the one I just pointed out makes no sense to me at all - what would be the point in adding a drum rack to a pad only to have other chains within it set to recieve on different notes?? surely the default situation in almost all cases would be to have them on the same note???
as for the first point, let me paste a PM conversation I had with Longjohns where we were trying to work it out - (if LJ doesnt mind of course!)
::::::::::::::::::::::::::::::::::::
Forge wrote:- you know the thread I posted yesterday you replied in about dragging to a chain list in drum rack? - do you have time right now to quickly have a look and see if you can work out if there is a valid reason for it or whether it's a bug?
here's the thread:
http://www.ableton.com/forum/viewtopic. ... 418#609418
I've just been playing around and it looks like it keeps happening until there is a standalone sample at the end and no drum racks
::::::::::::::::::::::::
Longjohns wrote:
I think it is probably intentional -
that if you drag to the chain list, it will make no attempt to guess what note you want it to respond to.
I can totally picture Amo saying "Craig, what do you expect in this case? Will the drum rack guess which note you want it set to?"
I'd say what they expect is that
1. you know what note you want, and you will drag to that pad
or
2. you will set the input note for the new chain after creating it
::::::::::::::::::::::::::::::::::
Forge wrote:
ha ha - true,that's sounds like Amo! Wink
but the weird thing is that at some point it does actually start following the rule of taking the next free pad
if you do what I did then drag a note to a free pad after all the others (so it's the last one) then drag a sample to the chain list - now it follows the rule
I'm just trying to work out if there is some kind of method to this
::::::::::::::::::::::::
Forge wrote:I'm starting to see a pattern
after steps one and 2 (single sample dragged to C1 followed by multi to D1) if you then drag the drum rack to the top in the chain list, then it works - the next single sample you drag into a chain list takes the next free slot
so it seems drum racks on pads confuse the count somehow - I just wnat to work out if there is any conceivable reason it could be meant to be like that
::::::::::::::::::::
Longjohns wrote:I see more what you mean now
It seems to auto-assign for only the top-level drum rack. And only once you're on a roll of adding samples, like you say.
If one of the top chains contains another drum rack, then it can't auto-assign around those notes.
But the top-level rack still gets its pads assigned by all the sub-racks which are set to 'all' at the top level.
Once you're on a roll of adding to the top-level chain list, it starts going up the notes like you say..
But it will still stack on top of an existing note, when it comes to an occupied note assignment (aka pad)
So I guess it does seem kind of buggy!
:::::::::::::::::::::::::::::::
