I know how frustrating software can be when workflows are wonky, not as expected, do not make sense or when basic features or great workflow improvements are missing. Also I understand that it can be frustrating when workflows and built up systems (e.g. folder structures) need to get adapted to a new UI behavior.qub wrote: ↑Thu Oct 24, 2024 11:50 pm
You guys can claim all you want that this is not a push to move to push, but it absolutely is. Otherwise, you would have left a classic interface as an option. And don't tell me there was no way you could do that, you only could move forward with this. That's a BS excuse. It may have taken a little time but you definitely could do it and if not you need to hire developers that can handle that job. You could, and should, still go back and add that as an option. It's not like you don't have the code from 11 that couldn't be adapted and integrated. This wasn't an addition to an existing browser that people were greatly familiar with and really didn't have complaints about. This was a complete wipeout of your existing browser and a forced move to something that a significant portion of your user base absolutely abhors.
It's not that we're having trouble getting used to it, it's that we don't like it. It is completely not functional for a lot of us and unusable in our existing
Though, a better browser has been requested over years. For Live 11 the issue (demanding a tagging system etc.) is ranked no. 14 (out of over 4k suggestions) on centercode. Also, I don't think that the Ableton Team has the hidden agenda to make ones live more cumbersome but that they actaully want to improve the software (also when sometimes it can take ages/won't happen at all for features to get implemented or it won't make everyone happy).
Maybe there are points for improvement on the current Live 12 browsing system. Maybe there are (hidden) workarounds. Maybe it breaks some workflows/structures (mine improved drastically instead). And of course that makes angry.
You have (or had, don't know) the chance here to write with one of the Ableton guys directly (what is really rare nowadays..) who is supportive, interested in your workflows and your thoughts about the browsing system and who seems to be interested in improving it further. I rather would use the chance to have a (maybe fruitful) constructive, calm and friendly discussion, instead of drifting to accusations, insults, yelling and telling Ableton what to or not to do. Don't get me wrong, I understand you. But if I was an Ableton dev./PM/whatever, don't know if I still would like to post here/take part in this discussion when it drifts off to an argument/impolite texting.
Also, please don't take my post personally. Just know it from myself that, when I am angry/emotional, I fast can write something which tends to sound a bit aggressive and where I later think maybe one or two levels lower would have been sufficient. Hope you can find a way to work with the browsing system and that it will improve for you