Is it me or is Push 3 not that great with the new Search Filters?

[Machinesworking]

Like the tittle suggests, I load a Drift into a track, then attempt to browse Drift presets, and it takes me to filtering EVERYTHING.
So how do you get Push 3 to just browse Drift Presets? because so far I can only do this if Push 3 is in controller mode and I use a mouse with Live 12.

[braduro]

Yeah, let's put our heads together. This is a real drag. First off, the problem persists in live as well, when you swap back to the browser. There is a way to preserve the last filter view or to switch it back on, but I haven't found that consistent, and you can't seem to do it from the initial preset selection. Nor can you autoload the next or previous preset from the filtered view before choosing the first selection and then loosing the filtered list entirely.

Not only is that a drag that it doesn't even preserve the instrument you're looking at. It doesn't preserve the folder you're looking at. So sifting through pads bumps you back to "all".

It makes browser preview an actual pestilent nuisance, due to the fact that the same jarring preset will play every time you get bumped out to the full list. It's like having your old iPod play that same damn song over and over again just because it began with an "A". Compound that with the volume of your cue mix, which is always defaulted WAY too loud, and it's like your microwave popcorn is ready every damn time you go back to swap a preset.

And furthermore, by loosing focus on the instrument you chose, as you pointed out, you could be loading up a multisampled simpler inadvertently, when you wanted to swap out other Drift presets. The former could lag your entire performance while the intended later would have been instantaneous.

There's an entire list of grievances with this new browser, which I'm hoping will be remedied with a revisit to the manual. Sonic Bloom does a "boring" thorough tutorial on sweetening the browser and making it work for you. But I wonder if it willl remedy these problems on the push.

[braduro]

One thing I'd test is whether you are initially loading new devices through "sounds" or "instruments" does it make a difference where the audition/swap presets browser dumps you out?
Ie, if you selected Instruments>Drift>Pads then loaded up a preset, then pressed swap, would it retain at least the instrument choice?

[braduro]

searched for "Filter" "Hot-Swap" " Load" "Folder" "audition" in the manual in hopes of finding some insight to retaining the last subset of searched items, be it a saved filter or the current device in context or the current folder, and nothing in the release notes nor the current rendition of the manual reflects the addition of filters nor how to audition/load presets from the current browser view. Nada.

Sometimes the auto load up/down buttons are available. Sometimes they're not, or only after you've loaded something in and get spat out to the unfiltered/ALL view again.

In other grumbles, I really dislike loading Sounds>Drum Kit and then observing that the filter options include things that are not Drum Kits, as if it presumes that I didn't really want a drum kit in the first place but rather something else

[Machinesworking]

searched for "Filter" "Hot-Swap" " Load" "Folder" "audition" in the manual in hopes of finding some insight to retaining the last subset of searched items, be it a saved filter or the current device in context or the current folder, and nothing in the release notes nor the current rendition of the manual reflects the addition of filters nor how to audition/load presets from the current browser view. Nada.

Sometimes the auto load up/down buttons are available. Sometimes they're not, or only after you've loaded something in and get spat out to the unfiltered/ALL view again.

In other grumbles, I really dislike loading Sounds>Drum Kit and then observing that the filter options include things that are not Drum Kits, as if it presumes that I didn't really want a drum kit in the first place but rather something else

I mean basically I have not much to add because you've done a great job of pointing out how broken the search function is for basic things in Push or even in Live.. Hopefully they get around to fixing it.

[jeanvoyage]

For me, not retaining the last opened folder is the biggest problem. It’s like the Push 3 doesn’t respect the fact that I don’t constantly want to browse my entire library. Especially annoying when trying to load drum samples in Drum Rack because every time I change the pad it defaults back to the entire library…
There should at least be setting for default behaviour.
This is literally a thing that might make me send back my Push..

[b-righteous]

Same here. The filtering is broken in several places. Hot swap just does not work as expected on Push and not consistent with the software. Browsing is tedious and it's a deal breaker for me. If this is not fixed soon, I will likely be forced to ditch push and move back to Maschine.

[Dadaunpa]

It's really frustrating, a hundred times better to search on Move. I'm tired of buying tools and being a Beta tester, never again!

[Machinesworking]

I really don't like being the naysayer here. There's so much to like about Push in terms of hardware. the MPE pads, the ADAT in/out was surprising and really pretty fantastic of them to do. I just don't understand why they're taking so long to make this thing a truly amazing experience?

Ableton are very obviously one of the most successful DAW developers out there, maybe the most profitable even besides Pro Tools. So it's not resources.

[braduro]

Anyone’s unpleasant experience is certainly recognized and valid. I do nonetheless wish to keep the subject of the thread unbroken.

The only current workaround is to nudge right on the big dial once you have your filter criteria and to save that search. Now does the filter include instrument-specific search results? Can I use “drift, pads, user” as a filter criteria, for example? I have to check. (We discussed the unwelcomed jolt of loading a multisampled instrument inadvertently or an untested m4l device in an instrument group for example, based on the indiscriminate search results)

But that saved search will then appear among my library. If I choose this Smart Folder when adding devices, Hotswap will then return to this subset. What I can stomach is doing this for the dozen or so obvious things that I reach for routinely. At least until ableton realizes how dysfunctional it is to work this way. Indeed sonicbloom works exclusively in user tags, perhaps for this reason.

[b-righteous]

I found the issue is with loading a drum rack, then trying to hot swap an individual pad from that. In this case, Push will not locate the sample or device that is currently loaded to the pad. This works correct in Live, but not from Push in controller mode. If I start with an empty rack, filter and load a new drum hit, then the hot swap works as expected from Push. The exception is if you go into hot swap, then switch to another pad. The filter for the new pad you selected will be off. You have to exit hot swap, select the other pad and press hot swap again for it to work right.

I assume the issue with drum racks may be present with any rack you load and then try to swap an individual element from that rack. So far I have not tested that though.

Also, Push in controller mode will always use auto tags even if that is deselected in the software. I thought the results were random since I would see hi hat sample names when it was filtered for kick. When auditioning, these were just named wrong and were actually kicks or other elements with enough low end that the waveform looked like a kick to the sound analysis engine.

[jeanvoyage]

I found the issue is with loading a drum rack, then trying to hot swap an individual pad from that. In this case, Push will not locate the sample or device that is currently loaded to the pad. This works correct in Live, but not from Push in controller mode. If I start with an empty rack, filter and load a new drum hit, then the hot swap works as expected from Push. The exception is if you go into hot swap, then switch to another pad. The filter for the new pad you selected will be off. You have to exit hot swap, select the other pad and press hot swap again for it to work right.

I assume the issue with drum racks may be present with any rack you load and then try to swap an individual element from that rack. So far I have not tested that though.

Also, Push in controller mode will always use auto tags even if that is deselected in the software. I thought the results were random since I would see hi hat sample names when it was filtered for kick. When auditioning, these were just named wrong and were actually kicks or other elements with enough low end that the waveform looked like a kick to the sound analysis engine.

So, better workflow is potentially just one update away. I sure hope so...

[braduro]

Here's one bug on the 12.2 that's squashed:

Fixed an issue that occurred when hot-swapping on loaded presets, where the browser would always jump to the top of the list.

I wonder to what extent this will clear up the kerfuffle?