I’ve not tried since the update. Are you have issues?
I returned my Move while I could. I was waiting for slicing.
I’m planning to get one again. I would love a bit more deeper editing of the synth. So I plan to create. Presets with macros that allow me to do it.
Some bass starter, pad starter, etc
You could do that since day one. Just not wavetable yet.
1 Like
I remember there were some issues. I didn’t managed to do it.
I’ve had no issues at all. I’ve posted loads of patches to this thread. I’ll post the bundle for you when I’m back home.
1 Like
Is anyone else seeing the same behaviour…
If you make a set, then rename the set via move.local, the set name changes instantly.
But if you make a set, build a custom drumkit, then save the set, then save/rename the drumkit, the drumkit name does not change in previously saved sets?
I think that kind of makes sense, if I’m following you correctly. You can set up a drum rack in a set and you don’t have to save that as a preset. It just lives in the set and is saved with it. You can put an instance of a preset in a set and change a bunch of parameters and that gets saved with the set but the changes don’t affect the saved preset.
So you have “Set 1” and you create your drum rack and name it “my drums” and save it.
Then you make “Set 2” and use that preset and make some changes and decide to rename it “dope drums”.
All future instances of it will be called “dope drums” but the previous instances are still “my drums”. Changes made within a set don’t affect every past instance of that preset, just any new ones moving forward.
Seems logical right? And same as it works in Live.
1 Like
I think it does. Because otherwise Move would have to search through sets and rename kits. Which, I imagine from a programming standpoint, is not ideal.
My workflow will now be to create a kit, save it, then name it, then create a set & load the kit… to keep name uniformity.
Also, I believe I witnessed the following behaviour: I created a kit and named it, “BLIP”. Then I made a change to the kit and saved it. Move saved the kit as BLIP 1, keeping both kits.
1 Like
Anyone of you managed to find a good compressor setting to simulate sidechain comp? Thanks!
How is the moving drum kits and presets from Live 12 to the move?
No, but I made a preset that pumps 
2 Likes
You can also sort of fake this with the 1.5 auto filter and a 1/4 LFO rate.
4 Likes
Well, I’m pumped for that!! Thanks mate
2 Likes
2 Likes
Looks badass
-
Live 12 Suite (+ packs) has a lot of great samples. Is there some easy way to access them via Explorer / Finder to copy to Move? They’re clearly not stored on the disc as plain .wav / .aiff
-
Do the new firmware versions add any new samples & patches (other than for new devices like Auto Filter)?
Those live packs are zips if I’m not mistaken. Or there was a tool to explore them. But the aiff files are encrypted somehow. You can’t copy them as they are. I tried this a long time ago.
1 Like
I have yet to try it out but found a way to get some pumping going. On the master comp Drop the threshold to the minimum, increase output volume and also increase you kick volume to max. Adjust to taste. It does sound a bit rough around the edges but it’s decent.
1 Like
On another note, am I correct in thinking that while I can sample my phone into the Move, I cannot record Move into my phone (while filming for example)?
Tried with usb cable + camera lightning adapter but no chance.
Thanks for your help
Some folks from the Ableton discord and I have been working on additional tools for the Move, available now on GitHub. These add on-device tools for restoring sets, sample slicing, chord kits, drum rack inspection and sample reversal. It’s open source and we hope to add more tools over time.
Here’s a demo showing off some of the features:
It requires a bit of technical work to get set up, but you can run this alongside all the built-in Move functionality on device. More on the repo~
18 Likes