So... the Max7 browser. Is very good.
It has all the things a modern browser for a complex and professional media application should have.
- It has tags and user tagging
- you can perform compound searches on tags and text strings (EG: Tags:[audio][audioplugin] "kick" , or Kind:Patcher, package:max for live)and the GUI informs you what is active in a clear, intelligible, intuitive and actionable way
- the interface is very immediately learnable, learned actions are repeatable elsewhere, and all user actions demonstrate Affordancevery well.
- you can search for your presets, in a specified date range, by your usage count, and by many other things too
- you can save all your complicated compound searches as bookmarks to re-use later
- you can create "advanced searches", and these are explained
- it has user "collections", IE: arbitrary non-exclusive groupings of stuff you might need in different circumstances
- you can add multiple list view columns, and sort on them, and this action is reflected quickly in the GUI with no awkward lag.
- It looks really nice and simple, but is powerful and flexible
- and lots more ...
https://docs.cycling74.com/max7/vignettes/file_browserCycling74 wrote: the File Browser has an easy to use search syntax.
Want to see all Max for Live devices created in 2014? That’s package: “Max for Live” after:2014-01-01. Searches you’ve made recently are available for easy recall, and if you’ll be looking for certain items regularly you can bookmark a search.
I'd just like to say a bigwell done, and a congratulations to the team who made the Max 7 browser. It is a very good example of a browser which must deliver appropriate content to many different sorts of people all using a complex application in many different ways and with different workflows. This browser makes a very good attempt and allowing all the disparate users in all circumstances to locate and access to their content and not to feel confused while doing so.
and then ... there's the Ableton Live 9 browser. squatting like a drunken malevolent toad on top of my content. I might be able to tie a string on my preset if I call it "angstrom_presetname_tagname_identifier" and remember to create a folder of the correct name to save it in. but that's no guarantee.
I hope that anyone who may be developing a browser would take a long look at the Max7 browser, especially if they happen to be making a browser for a complex application which must serve many disparate usertypes in different circumstances.
I hope that this time around Ableton are less defensive about obvious flaws, and a bit more proactive about investigating requirements and delivering a product fit for use
Otherwise they might produce another unusable abortion.