This was driving me crazy and thanks for starting the discussion. I am glad it’s not a “bug”. But I hate it.
And speaking of other DAWs. In MPC Software you can only choose one scale. If you change the scale in a new track, it changes all of them to the one you just selected.
No worries, and appreciate @Rivanni summary. I understand.
Still feel like I’ve seen at least ‘unexpected behaviour’ if not a bug since I was able to watch that parameter change by itself in my described interaction…then knocking out a series of Scale devices all ‘tapping’ that setting…if that makes sense. Will track/report it if anything similar happens again.
v12.1.1 is out and (hopefully!!!) it is designed to stop the hang on startup. Obviously a few folks sent in the reports and they’ve tried to address it.
How’s 12.1 feeling stability-wise? I’m still using live 11, but do have a license for 12… was thinking it would be “mature” enough to switch to soon, dont feel like betatesting my main DAW since I also use it for work stuff…
The auto tagging in 12.1 is pretty nuts. I’m digging up tons of old little discarded weird little percussion loops, sound fx, synth lines and whatnot from the browser that are getting a second lease on life thanks to the magic of autowarp.
12 has been rock solid, but there’s some things to be prepared for.
Keep in mind you can continue to use 11 alongside 12, but it’s good to know that 12 will scan connected folders for use of the sound similarity search and it can take awhile the first time. You can also pause this if needed.
Some people have had difficulty with loading templates created in 11. Some have experienced hanging when starting. Most of these issues have fixes with deleting Live’s database. There’s other fixes if you run into these things.
on sequoia from day 1 no issues whatsoever, live 12, overbridge, max, none of the plugins broke, motu works fine, there was a thread with some software problem reported but iirc it was fixed by developer
question about meld modulation matrix, any meld users here?
working on a project I run into some inconsistencies that are annoying for me, the kind of distractions not good for my creativity.
when I connected push 3 I noticed that the values shown on push are different from the values shown on the computer screen in the modulation matrix? I was super confused, first I thought I am on the wrong track on a different instance of meld…
I wanted a ramp lfo mapped to volume, expected the lfo to deliver a value that covers the full range, but the impact is quite minimal? is this normal behaviour and why?
compared to other software the visual feedback in live is really way behind. in bitwig mapping an extra lfo or envelope to a volume knob is quite intuitive. really hope ableton is aware. many of the new features seem cool at first but in detail it’s not so much fun to use
I know this has been covered before and I did try and Google it, but I didn’t discover the hard and fast answer.
I love using the new Generators, specifically MDD Snake Generator. I create patterns that I love and then when I come back to my session after restarting Live, that pattern is gone.
How do I keep the Generated midi pattern in place? Ideally I’d like to not have to flatten it because I like having the “setup” of MDD in place in case I wanted to create future variations based on the configuration of that specific device.
I’m 100% sure there’s an easy way to do this that I’m missing. Historically I’ve created a second midi track, set it’s input to the Generator’s track and then recorded the pattern into that track, but in 12 there’s got to be a better way, yes?
If anyone has a simple solution, I would be so grateful to hear it.