As I seem to be in the minority of absolutely loving the new browser, maybe I just didn't figure out the previous one efficiently?

So my workflow is: browser closed when working, then ctrl+f, type plugin name (normally just a few characters will do) or type a sample name and pick from the list, drag to a track, close browser (either ctrl-alt-b or an extra mouse button on the side), carry on. Sometimes the fastest way creating a new track and adding plugin: ctrl+shif+t to create and focus to a new track,s ctrl+f <instrument name>, select from list with down arrow, enter to insert, alt+f4 to get rid of the plugin window, ctrl +f <effect name>, select from list, enter, alt+f4, ctrl+f +f effect name>, select, insert... Then close browser and carry on.

Now with the new browser it's same with two extras, if I'm not sure what I'm looking for after installing new plugins I can narrow it down with the categories (say, I want an effect, not an instrument, and I want it to be a VST3 plugin, and it's from developer XYZ) and then look it up.

I'm using the autogenerated tags, and my normal color labeling, so no extra work from me.

If I'm browsing sounds, I can specify those, search for a bassdrum or whatever, get a list of sounds (nice thing is as well that Ableton's racks contain a preview as well), start looking for a suitable one, when something in the same ballpark perks my ears, click the "show similar" button to let Ableton show sounds by similarity. This works surprisingly well.

So, for me I can use my old way of working, but have those two new features making it even better. No way I would consider the old one better.

 

For me Ableton 12 is a mess. I get a lot of random CPU spikes. Even with only a few simplers playing drum samples. It does not loop correctly, like every 30 seconds there is a loop that does glitch a lot when it goes back to the start. I have a 13900k, so it should not be the processor. I really am not sold on it at all right now.

Anyone else experiencing anything like that?

Then again, I didn't bother to update to the newest beta version, I think I will just wait until they fix it properly

 

Yes my friend, together with making my folder structure of tags

 

Huh, I've not encountered any weird CPU use/spikes myself, not even with the new instruments/effects. What was the version of the beta you tried, if you can recall?

I've not done any benchmarks or stress tests though, but it looks to me that it runs the same sets just as 11 does.

But yeah, fair enough not wanting to try the betas anymore after a bad experience... I think the final release will be out soonish, so maybe wait for that, or the couple of point releases after the "mass beta".

 

March 5, 2024.
Make room for it @Bunford

 

Last edited: Feb 21, 2024