So I’m not crazy. Thank you. I hadn’t yet thought to test the inputs and outputs separately.
If the issue really is the output we’ll have to hope for a firmware fix. There’s no way I’ve found to adjust output levels in the same way we can adjust input levels via settings.
Even with the input gain turned to to +20db it still sounds soft and muddy. I’ll have to switch back to taking up more I/O on the 18i20 and avoiding the Push I/O until this is resolved.
I’ll probably write to support to see what they think. Let me know if you figure anything else out.
Are the OTO boxes meant for guitar? It could be that the return signal is mismatched to the Push’s line ins.
When you plug a guitar into a non Hi-Z input, it’s not only quiet, but sounds weak and thin.
I also notice that the OTOs use unbalanced connections. With some audio interfaces, using an unbalanced cable/signal with a balanced input can also result in a volume drop.
The input jacks can be switched between three preamp types: Line (balanced); Instrument (unbalanced); and High (a higher gain instrument input, unbalanced). For each input, there is also the option to add another 20dB of gain digitally.
is it a known issue that midi sync in does not work? I can not get push 3 to respond to midi start/stop/transport from any other midi devices, but Push 3 can send midi out just fine.
In the meantime I have submitted a second ticket for the issue of the jog wheel randomly not selecting notes in clips view - they closed my first ticket for this without even attempting to address it. It will lock up and just refuse to do anything on any clip. Can’t select notes, can’t select all, can’t move anything around. I’ve even checked all of the clips on a project to see if maybe it somehow got “stuck.” I can’t identify a specific cause. Sometimes reloading the project fixes it and sometimes it doesn’t. Usually I have to load a different project and reload the original project. If that doesn’t work the only fix is usually to turn off the push entirely. With the extremely long boot time of the Push, this is a real momentum killer.
This time I included a video of the problem happening, me selecting and deselecting all notes, switching clips, etc. Hopefully this ticket actually gets taken seriously.
I’m on the regular release, and editing notes in clip view is the only place it locks up. Every other function using the jogwheel works just fine. Navigating menus, renaming, navigating session view, choosing instruments/FX etc all work correctly.
I haven’t had this happen in the clip view yet, but I know I don’t spend a ton of time editing midi events in Clip View.
Usually it’s just to adjust velocity or pitch on a single note.
Have you or @m0ld noticed if there’s anything specific about the clips you’re working on? Like are midi notes overlapping, multiple chords, or lots of quick short notes?
I know @m0ld said it was random, but I thought I’d ask just in case there’s something that seem similar when it stops working.
I’ve tried looking for a pattern, and I can’t find one. Chords, overlapping notes, no overlapping notes, drum programs, ableton’s synths, sliced simplers, clips that were programmed on the step sequencer, clips that were live recorded, clips I used Capture to get the midi, clips I’ve never edited, clips I edited extensively, switching between certain clips. I really can’t find a reliable way to reproduce it (and thereby potentially work around it). It’s even random when it will happen - sometimes it happens immediately, sometimes I can go 2 hours before it strikes.
That doesn’t mean there isn’t a pattern but I certainly can’t find one.
My suspicion until today was that maybe it happened if I didn’t hit “Done” when editing midi info and then switched clips, but that turned out to be a nonstarter - I did so several times and it didn’t trigger the glitch. Then it struck later even though I was being very careful to hit “done.”
As far as I can tell it’s random, but most of my work is sample based. I usually get the 808’s in one take, but I had a client that was very specific and requires lots of editing and it was a mess.
For me it also occurs seemingly random and I had the same suspicion that not pressing done was the root of this evil because sometimes I was able to “fix” this by going into another track, selecting a note and explicitly pressing done again. Other times it made things worst though by occurring on that track as well. Let’s hope they closed the ticked because they fixed it already since this is the most annoying bug I saw on the push as of now which often lead to throwing away the wip project.
Yes, it would be easier to work with (when you know tempo) to simply have Ableton read the tempo and then you can crop the tail out at the grid point and warp from there. It works that way in the software. Maybe my answer is I will just have to prep all of my samples in Live before sending to the push.