Ive tried to get 96khz sampling working on the 18i20. Did you have any success with that?
I managed to get it going with 48khz
Ive tried to get 96khz sampling working on the 18i20. Did you have any success with that?
I managed to get it going with 48khz
There’s a setting in Focusrite Control that determines optical port behaviour that allows 4 channels at 96kHz for ADAT instead of 8 at 44.1 or 48. It’s not selected by default. I haven’t tried it, but as I understand it, you’d need to have that option selected in as well as having both Push and the 18i20 running at 96kHz.
Yeah gave that a try but dead silence. Weird.
I don’t know what it could be honestly - I’d assume that would work too. It may not be, but in case it’s useful somehow, I’ve described how I set up my routing for the 18i20 in this post in the other thread.
Done that. Doesn’t solve the issue.
I can dial and “left-click” perfectly but the “right-click” requires heavy pressure and is not always reliable. This is ok when accessing the context menu for example to delete files.
It becomes unusable when you need to perform that gesture more often for example when renaming a file and skipping through a text.
Even with jog-wheel off the functionality is not given.
Edit: Ableton Support was super-quick (give the amount of requests they might get). They will exchange the device.
My personal take: This can absolutely happen and Ableton is responsive & fast. Still a hughe fan after the first days with the device and definitely looking forward for the things to come.
What I’m really missing is some kind of visual feedback of the master level in the hardware, just like in MPC X or just a tiny led bar like in Op-1 Field, that would be perfect for control the levels easily.
Had the ‘Unexpected’ start up message, but otherwise so far so good in standalone - haven’t tried in control mode yet, or with adat and midi hub connected
Yes, it definitely works. Here’s a proof:
For those with controller versions, do you also get the “user mode not available in this software version” message when you click the button?
I expect so as it’s the controller version but thought I’d check as I have a few other system menus missing (like wifi) which I presume is purely due to the whole controller vs standalone thing. I’m just scraping the barrel here for things that might be driving issues…
This common initial experience brings new meaning to the phrase ‘expect the unexpected’.
Thanks! Gave it another twirl. Looks like a limitation on the push. I can see the audio in volumes on the 18i20 - somehow it even works with the 18i20 to 96khz and the push on 48khz.
Anything above 48khz on the push doesn’t work.
Edit: fun fact, 18i20 on 96khz and 48khz on push makes a mono signal show up as stereo incoming audio on the push.
I had the issue with expressive choir only available as paid pack. As soon as i authorised a second PC with ny newly bought suite license i was able to download it. Just FYI
Nice video–I like how you are explaining things as you are actually using the Push 3 in real time to create something new, from scratch, including all the raw elements of having to back up and do things over or differently. Puts me right there with you.
I bring good news from geek central.
I established the new USB Device ID for the Push 3 and then hacked someones Push 2 code. I was then able to drive the display of the Push 3 in exactly the same was as was possible with the Push 2. So this stuff isnt locked down and third parties will be able to work their magic. I already told the DrivenByMoss developer about my findings.
Sounds interesting! For those of us who are new to the Push, can you provide a brief summary of what sort of new capabilities this might open up? Or perhaps suggest some links where we can dive in to find out more?
That’s really exciting to hear, thanks for doing the research. Will be even happier than I already am if I can use Push 3 directly with Bitwig in the future.
DrivenByMoss is the most famous example (and lots of youtube videos exist of the functionality added to each new version of his software), enabling users of Bitwig and Reaper to use the previous Pushes.
https://www.mossgrabers.de/Software/Software.html
Other examples include an opensource sequencer that someone made that can run on a raspberry pi hooked up to a push 2:
There will be other examples but I am out of date with that world, having dabbled with my own code simply as a learning exercise years ago. Although the focus of these projects is on using Push for non-Ableton Live purposes, there may also be examples of mixed systems out there where additional functionality might have been added to Live, for example via the User Mode, a mode that I have completely forgotten the details of these days.
Best yt synthsdxxzz channel
I’ve got an answer from ableton yesterday that they were aware of the issue and investigating it whether if it’s a hardware or software issue - suggewsted me to update the device for now. Although it was a copy paste answer as they’ve referred me as ‘Paul’ which is not even close to my name lmao. And also skipped my other two questions about unresponsive pads and loose jogwheel.
Unfortunately even I’m on the latest firmware, it happens infrequently to me. I suspect it’s a hardware issue. Already collected a log WHILE this is happening and sent to Ableton as a follow up for my previous ticket. Leaving the video as a reference if someone ends up here from google ![]()