Along the same lines, is anyone aware of standalone-compatible sequencers that produce random patterns that can also be tweaked (basically, devices like Sting). I’m really enjoying Sting, although it’s designed to specifically do that acid sound and thus is a bit limiting. (The Push-compatible version is also only 16 steps).
I use a bunch but manifest pattern engine is my main go-to, set up with dummy clips to trigger the various randomisation options. Usually in trigger mode so that the sequencer is advanced by clock or Euclidean sequences sent from either manifest octapulse or rotating rhythm generator.
I also use ACDGen but unfortunately the really cool feature of controlling four instances from push in user mode doesn’t work in standalone, or at least I haven’t been able to get it going. Quite similar to sting, just with a few more options. Nice for a different flavor to the manifest stuff.
I think you have to come off the beta and go onto the official release to get any future updates…… is that right?
Open to correction, but I don’t think so.
There was a thing where I had to reauthorise push in order to install 2.0b29, but b30 installed fine after that and works with a full version of 12. 11 betas are 1.* - I’ve had meld and roar in standalone for a while.
I guess I’ll find out for sure when the next beta release drops.
When you are on the Push 3 beta channel, the next update you will receive is the next beta. (not available yet). So you will not receive the 12.0.1(Push 2.0) update.
If you want to switch to the release channel, you will have to download the 11.3/12.0.1 *.swu file and install that file via push.local/update. After that the next update will be the from the release channel.
Just updated.
Is practically the same as beta.
They didnt even fixed the Routing CV Instrument to allow to use stereo… my modulars are stereo… reported ages ago.
These things are heavy reported in the center code beta testing and are not addressed yet:
- CV Instrument calibration not included.
- Granulator III not able to load samples yet.
- CV Instrument just routable from mono input.
- Dr. Chaos still not showing all options.
- Envelopes / LFO not routable yet.
- CPU meter not included.
- Sampler not showing waveform
- Sampler not able to load a sample
- Live 12 Euclidean generator not included…
- Intstrument Racks and Effect chain racks not implemented…
Pretty frustrating. Im pretty sure that the VU Meters bug is still there. I honestly don´t know what these people is working on… Trap Drums and Golden Era Hip Hop Drums?
I thought with the release of the official version of 12 for the push that we now no longer have a beta stream.
Is that incorrect? Even though live 12 is officially released, they’re still running a beta release stream alongside the official release stream ?
Like on my mac, I switched to the official 12 release. Does Live 12 for computer still have a beta release stream also?
Both Live 12 on the Push and PC/Mac will have new beta updates.
I was unaware.
I though that once official
was released there were no more betas.
Thanks
You jump in and give it a crack then
I didn´t understand.
But its frustrating. I spent so many hours reporting bugs, sending and reading logs, implementing workarounds, sending gb of sets… (QA testing and AIV is actually a job) to see that something that should be simple to be implemented is not fixed yet. Most of the code is already done.
This is a weird one. I saw it and thought “huh, I use rotating rhythm generator in standalone all the time”. But then I went in to try to add a device in standalone and it isn’t there. Makes it even weirder that I usually avoid “collect all and save” with my live sets out of habit because of the thing where it used to create loads of different versions of my max devices, so I don’t think I’m exporting the device with my templates. I guess it must still be there in the pack but not visible.
Can see how the calibration issue would be very annoying, but is it not possible to do it in the box and save as presets for each oscillator or semi modular? Load the preset, use a tuner to set the oscillator pitch and it should be good to go?
And set up preset racks with macros already mapped and additional modulation devices if required? Isn’t true that racks and macros aren’t implemented, you just can’t create them in standalone … but why would you want to anyway? Seems like a massive pain in the ass to me. Some of the stuff is down to max, e.g. the granulator thing.
I guess it comes down to how you want to work, but to be absolutely honest this list seems kinda minor compared to some of the other stuff I’ve seen bothering people to do with midi editing, etc. I get that it’s annoying if you want to insist on 100% standalone and never plug in to the DAW that the device is currently set up as an extension of Live that pretty much assumes you’ll do most routing/patching type tasks in the DAW before exporting.
Maybe that will change, but it would involve adding a lot of UI stuff that isn’t currently there. Doesn’t seem that simple to me, and it seems a bit unfair to be going so hard about a list like this considering that there’s been a lot of progress even in the three or four months that I’ve had mine.
Blockquote
Can see how the calibration issue would be very annoying, but is it not possible to do it in the box and save as presets for each oscillator or semi modular? Load the preset, use a tuner to set the oscillator pitch and it should be good to go?
Yes. There are a lot of workarounds. Using push3 standalone is about workarounds.
For this I do what you pointed, but it´s a pain since you have to change the soundcard preferences to do it.
Blockquote
And set up preset racks with macros already mapped and additional modulation devices if required? Isn’t true that racks and macros aren’t implemented, you just can’t create them in standalone … but why would you want to anyway? Seems like a massive pain in the ass to me. Some of the stuff is down to max, e.g. the granulator thing.
If transferring sets would not be a pain, it would be ok. However if I use this device as a standalone device, sometimes during a sound design session you have not the DAW near. And you can´t easily duplicate a effect chain into another track since you can´t save the Effect chain rack. I´m not even looking forward to set macros.
Blockquote
I guess it comes down to how you want to work, but to be absolutely honest this list seems kinda minor compared to some of the other stuff I’ve seen bothering people to do with midi editing, etc. I get that it’s annoying if you want to insist on 100% standalone and never plug in to the DAW that the device is currently set up as an extension of Live that pretty much assumes you’ll do most routing/patching type tasks in the DAW before exporting.
That´s how I´m using it. But it´s not the promised thing. Transferring sets is a pain, sometimes fails during the process, is slow (several gb per set) and when you forget something or set something wrong you have to transfer it again…
So, yes we are using that way, as a extension of the DAW, as a performance machine where you have almost everything prepatched… but it was intended to be a standalone device.
Let´s see how this device evolves, but I won´t be participating on reporting bugs anymore. I´m tired. I think Ableton tried to do something over their possibilities.
I´m, not trying to rant over. I`ve been actively helping people to workaround since the Push3 standalone release date.
I´m just a developer giving my POV during my beta testing participation after a lot of time spent in the bug reporting.
Also this device is pretended to be something professional I use it for my work and the state it was released was a joke, so I don´t understand why a opinion is not accepted. Has been improved thanks to people who bought it reporting actively bugs.
I won´t participate here anymore. I´m not looking for a moderator intervention.
Yeah look, I’m just going to have to disagree with you here. When I compare where Push 3 including standalone mode is compared to other gear I went in on early like the Rytm and MPC Live, it comes out very well. Especially considering how much more complex it is by comparison.
I’d actually planned to hold off on getting one until at least the middle of this year to allow it to mature a bit, but then the 20% off sale combined with a good offer for my Push 2 made me take the jump earlier and I’ve been pleasantly surprised at how smooth things have been.
Getting past the hyperbole, it works well on its own terms, even if there’s obviously room for improvement in a lot of areas - especially file management as you mentioned. But there are solutions to a lot of the issues that are commonly raised, even though usually it involves doing some patching in the computer. You can just as easily see that as workflow rather than workaround.
I guess there’s still an open question as to whether it’s ever going to be the full fat Live in a box experience with every single function of the DAW available. But as far as I ever understood it, this was never what Ableton promised. And more than that, to my mind it is highly questionable whether that’s even a good idea - it seems likely to me that if they’d gone down that route straight out of the gate people would be complaining about bloat like they have been with the current-gen MPCs, with probably a lot more bugs and issues into the bargain.
Anyway, everyone’s entitled to their view. This did give me a prompt to go and do a long-overdue review and update tidy up of my presets and racks with a view to relying less on fully built sets as my starting point in Push, so that’s all good.
I don’t feel conned, it’s ok and I bought what I bought, but I do feel standalone is more incapable of standalone work than I expected. Still no song arrangement tools. Lots of things incl external controller knobs can’t be set up. Etc.
This may be something to do with the gen/tran params working on a global/project level rather than on the individual clip level. So, setting and changing the gen/tran settings in one clip is also mirrored across all other clips in that project, which would in turn mean that mapping a controller to any of these params would just end in a confusing mess. I’d love to be proved wrong on this as I was anticipating the midi tools working on a clip level and the fact that they do not is kind of a bummer for how I like to do things.
For me, there are a few obvious things lacking, like the ability to change the default collection names, or being able to map the LFO, or the External Effect in/out, but I’m sure those are coming. And not being able to change the default set is nuts.
Otherwise, I think the Standalone is great. It’s surprisingly different from using it as a controller (which I also love), and focusses me in a different way. Right now I’m still getting my setup in place so there’s a lot of back and forth as I create racks and map macros, but it’s already made all of my other hardware obsolete, for now.
I’ve said this before somewhere, but if Elektron added the ability to deep-program the Octatrack from a Mac/PC app, and save the results to the hardware, then it would be seen as revolutionary. And yet when the Push does this, everyone complains that it’s not a full DAW in there.
First, I don’t see why you’d even want a full daw in a box when laptops exist and are way better at it. Second, a few moments thought shows that there’s no way to put all of Ableton’s features into the Push without seriously compromising the UI.
I hope that will add Groove Pool at some point. For me the biggest downer of P3 standalone in it‘s current state.