I found where this Midi Probabilty device is from. Someone made it following this excellent tutorial.
That sucks. Curious to see what the reader outputs. Could also give Apple support a call and ask what the TB ports output?
Edited, realized you have the 14 MBP, not an Air.
Just wondering, are people using Live Beta or standard release for the Push SA?
I ask as I’m currently using standard release, but single 11.3 can no longer install packs, it just hangs, and I’m wondering I think the Beta address this issue, but don’t want to use it if it does not work great with the Push SA.
The beta installs separately and you can even run the standard release of Live and the Beta of Live at the same time.
But standalone will still work, I assume you mean transferring sets from Live to Push, but just don’t uninstall the standard release just in case you run into an issue
So that tester meter came and it’s not conclusive… But possibly indicates 2 issues.
I firstly plugged it in and using the Ableton cable plugged my iPad Pro (4th gen) in. This spat out (roughly) 5V, 2.8A and (potentially disappointingly) 13.7W. Not sure I’ve got anything else that could “force” test a 15W power delivery.
I then plugged in my P3C. With no power cable in I can see a shade over 5V going into it but no A or W at all. These results are identical when powered on via the power supply.
I then tried the “fancy” usb cable. Results are similar though at least with the iPad it’s registering over 14w (not quite 15 though…)
Both device and cable showed some odd behaviour with Push and no power supply - they both would flicker on for a few seconds then off almost like it was rebooting/restarting a connection and getting nowhere (if that makes sense).
So I wonder if I have a problem at both ends with my MBP not quite pushing out enough watts but the P3C not recognising/communicating to “request” a power drain or something. Dunno the tech term for that if there is one!
oh man, thats too bad you didnt get much futher. Well the iPad did negotiate the PD spec but not quite 15W, so I would say the Mac is working. Can you try another non-Apple device to see if the USB C port is working fine.
Do you have a USB C PD power bank to try with the Push? If it powers on and draws 15W from a power bank then you know its something funky between the Mac and Push but if it doesnt do anything, then you could assume its Push.
You have an Ableton group where you live? Maybe drop a line to see if someone else who has a P3 wants to meet up?
Can someone test if its possible to copy and paste notes with automation on P3 Standalone (or even controller)?
I just discovered its not possible on Push 2 and was wondering if they added that yet.
Copy/pasting notes isn’t possible at all on Push right now, sadly, unless I’ve missed something huge.
Unfortunately I don’t have a power bank. That’d be one solution to where I’m at with things.
I’ve shared the findings with Ableton so will see if it triggers anything or if I hit a brick wall. Totally appreciate that solving tech issues isn’t easy and involves plenty of variables so not the end of the world plus they have indicated again that I could return and “upgrade” to a standalone. Pretty tempting to be honest but would like to bottom out my problem as best I can.
On P2 its hold Duplicate button and press step to copy, then press destination to paste but that doesnt copy automation.
Still no automation copied, even when it’s added at the step level. I tried it on both Drum Racks, and the melodic sequencers.
@m0ld - you just can’t copy/paste multiple notes at once.
As of now, the only way is copy/paste in the sequencer modes. Using the jogwheel in Clip Edit won’t copy anything, but once you change the layout, you can (holding duplicate+step->empty step (while not letting go of duplicate). The screen will show the note is copied and pasted.
It’s definitely not ideal, so I hope they’re planning on building out this workflow for copy/paste and absolutely… would love to see automation copied too.
On the Elektronauts boards, nobody here is unfamiliar with copying/pasting trigs with all its variations. It’s one of the reasons I won’t let go of Syntakt.
Getting rid of Digitakt, was filled with compromises in working with Push, but I’m okay with this at the sampling level.
Just got my Push 3 (non Standalone ) today. I have been playing with it all morning and I am impressed so far. One thing that does not work is if I connect my op-1 field via the usb a on the push it crashes . But I feel its early days and this will be fixed eventually. I tried connecting my 404mk2 and it works perfectly.
No chance of VSTs on standalone?
Wouldn’t bet on it. The UI side of things would be pretty difficult.
I don’t miss it, the stock stuff is most excellent and some more esoteric stuff can no doubt be handled with M4L devices.
My Push 3 (non Standalone) waits for me at home (I am at my cabin until Saturday). I had thought about cancelling it, but then Ableton shipped it out before I got around to it, so I will try my unit to see what bugs it might have. Is there a single place, here at Elektronaughts or elsewhere, that comprises some kind of list of things to check to see if your specific unit has one of the several known hardware flaws? I know about the mod strip issues, the USB cable issues, the jog wheel issues, I think there was also maybe a volume knob issue (but maybe some of these have been resolved in firmware updates). I can’t remember now what others have come up. I’d like to test mine out while I can still return it.
The pitch/mod strip issue was fixed in a firmware update.
I think you’ve come as close to writing up a list!
Someone mentioned triggering the bottom left pads when pressing on the touch strip.
I haven’t had that problem so I’d check that too.
Ahhh, right. I was specifically thinking of the jogwheel. I forget that you can copy paste in the other layouts.
Certainly a few users reported certain pads triggering other pads too, though not too many reports of that. And then later there was some change to the way pads behaved in a firmware update, but I’m not sure whether that fixed these issues that a few people had or not. Its harder to build up a proper picture when not many people are affected.
Yeah, seems like a missed opportunity
I keep hoping there will be an update at some point that makes it an option.