Yeah I was just thinking today, the jump from 11 to 12 seemed to bring a lot of changes to the foundation of the program, whereas 12.1 introduces updates to devices and tools. I wonder if it was always planned to be this tiered approach?
Edit: I think maybe the seemingly lukewarm reception on the Push might have driven them to really knuckle down and push out some bigger updates to the software to win back favour?
Thats good to hear. I was an early adapter to the Push 3 and ended up returning it. But I am quite sure that itās much better now. When I had it, it was pretty bare bones. I am just not sure how much I will use it.
Hoping they come out with a smaller version that is also standalone. That would probably push me over the edge.
Iāve been holding off from installing the beta and doing my work in it because I wanted to make sure that everything was stable.
At this point, my impression is that lots of people are working in it 24/7, is that correct? On a scale of 1-10, how stable are people finding the beta at this point? Would you recommend installing it and working in it as my primary install? I donāt have any release deadlines or anything like that, but I hate to lose work and I hate instability.
I would love feedback. It sounds like a playground and Iām experiencing major FOMO and canāt wait to get into the new tools. Thank you in advance
If slice shuffler is a repackage of the free Phrase Shuffler, that is a great little addition. Think of it as an auto chopper for breaks/samples. Slice to drum rack, then randmise the slices, but as with all the new MIDI tools you can just continue doing this until you find something you like Iām sure the others are great.
Iām pretty sure I got close to this (the crossfader) with Clyph-x a few years back. Was one of the tings I really loved about the OT, so tried to recreate a similar behaviour.
But the project is long gone now, just saying this because I am dogshit at programming in general, so something like it should be achievable by someone with moderate skills.
You will, no problem. Later versions always load projects from earlier versions. Itās the other way around that doesnāt workāyou canāt open a Live 12 project with Live 11 for example.
Yeah being in the beta now seems somewhat lower risk. Youāre basically trialling a future update early, where the difference between 11 and 12 could easily mess with projects.
Does anyone know if itās somehow possible to save a device with midi mappings intakt when you open them in a new project?
The reason I ask is that I keep encountering some bugs (probably caused by m4l devices) where for example some push functionality will stop working. Only way to fix it is to create a new project. Not such a big deal to load up the devices as there are not that many but doing all the midi mapping again from scratch really sucks.
Im in it now. The Auto tuner is great. I have barely dove in yet to all the other features, but this is an incredible update so far.
For some reason I canāt find the .alp files you can download with the beta. I drag them into a session and it shows they are installed, but when I search for them, I canāt find them. I have to be doing something wrong. Not sure if itās a Mac permission error or something else.
One ābugā (not sure if this is fixble tbh!) Is that when loading some packs - including those new sequencers - into Live 12 beta, they actually show up in Live 12 stable release for some reason. Can be worth a quick search there.