I had lazy moments in my life. I was called lazy. I didn't mind that, because it was true. Leaving easy things undone when the most difficult part is completed IS lazy, because at the end it's little details that decide about perception of how your work is received.apoclypse wrote: Tue Dec 29, 2020 10:09 pmThen you should know how disrespectful and frustrating it is for someone to call you lazy because something doesn't work the way they want it to without knowing the kind of work hours, time and effort it took to develop the application in the first place. Playing arm chair developer, especially when it comes to commercial software doesn't help anyone.
So, how about we call a spade a spade (or whatever the saying in your country) instead of bothering ourselves whether or not it's offensive?
I try. I do my best. I don't know or understand everything. I might also be just plain stupid.apoclypse wrote: Tue Dec 29, 2020 10:09 pmYou also can't seem to understand that some people actually like the way things work or that the developers just have a different perspective about how things should work.
Yes, I'm dead serious. The way you phrased it opened my eyes to why it's implemented like that. I'm still unsure I prefer it that way, because e.g. in Bitwig you could choose by either selecting clips or selecting time that included those same clips. In S1 you can sort of do this too, by either using Transform or Mixdown Selection.apoclypse wrote: Tue Dec 29, 2020 10:09 pmNot sure if serious but if so when you re-transform the track back to an instrument or realtime state, it will keep the changes made in position, cuts etc. Again most freezes don't do that. That's why S1 renders each clip individually. It has to keep track of all that data and still be able to change back to an instrument track when necessary.
I really think this should be mentioned in 'Fundamentals' section of the Reference Manual, as it is somewhat special and unique.
Yes, you're right. My perception of this might be - is - skewed because I'm not really a musican / producer, but rather someone who finds most joy in trying & learning music software, so I naturally tend to compare them and look for ways to "improve" them, at least from my limited perspective.apoclypse wrote: Tue Dec 29, 2020 10:09 pmConsidering most DAWs don't do this I guess it doesn't matter does it. S1 is doing what everyone else is doing in this regard and if you think they should change that then get in touch with the developers. No need to rant on banging the drum when nobody here can do anything about it anyway. Considering the only handful of responses (mostly people criticizing your posts) then it look like people don't actually care that much about these issues.
The fact that a feature works in certain way elsewhere and very few people complain doesn't mean it's perfect and cannot be improved. There was an interview with Ableton devs where they described watching users work in Live on laptops, getting really embarassed to see people awkwardly and clumsily trying to zoom & scroll stuff by dragging the beat bar. So they decided to add touchpad gestures, even though barely anyone asked for them (I did, that's why I left for Bitwig before v10 was released). Likewise, barely anyone on Ableton's beta asked for alias/ghost clips in Live v10, because most people have been using it for years and it never had them, so they had no idea such a thing even exists. But when feature request with proper description of the feature was posted, it landed in top-10 requests (out of hundreds), because people understood what it's for and how it can help them.
So I'm sorry, but I just don't buy an excuse that shared clips should stay the way they are, because Cubase does it like that and other DAWs too
