Default Instrument Name And Icon

The instrument factory pics are nice but you can’t see them when your tracks are sized skinny. I thought to put an emoji in the name show the instrument type. Does that mess with the filename? Any issues?

That piano icon displays the track type, yes? Not sure why because the color tells us that already. So that’s where our custom icon should be, per plugin.

So that you can put the preset name as the track name, the icon will tell you what plugin it is, and the track color tells you the track type. So you get all that info at a glance.

I tried emojis with a couple different icons and they look not bad:

Emoji

For GA6 I would make it have a drums icon and name as a default template. Is there a way to set up template track names and pictures so they are auto populated in the dialogue?

And can we give plugins an alias name, so we can customize how they appear in menus etc. ?

The track’s color doesn’t tell us the track type. Maybe you work like this but many other users don’t.

The color does tell us the track type:

I’m brainstorming how to get an icon system for the tracks. A large picture=large track / small picture=small track system. I don’t think emojis would be a good idea, and I wouldn’t want to type them out every time.

Colors are a piece of information, not just for looks. If we would do the color for one thing and the icon for something else, that makes sense. Currently the track icon is telling us the same thing the color is. Why not divide them, so the icon can tell us information, like what plugin it is or something.

Track colors link up with the event colors so it’s more important than icons. And our brains process colors faster than anything else. So I’m not yet sure how to swing this.

Again, you might be using track colors in the way to identify different track types. Most of the screenshots and videos I have seen from other users use the track color in a completely different way.
My prefs look like this:

If you are trying to figure out a better way than the current one you should try not to alienate users with the design.

Ah you’re the guy that tells everyone their suggestions are wrong cause that’s not how you use it, and you are the master of the universe. Every forum has one.

Maybe those who seek the best way *should be alienated from those who don’t, so our legitimate progress is not slowed down without cause.

I recently realized that this could also be used to sort items as a database, like the media bay. There could be an optional sort header at the top with columns and you click it to sort ascending/descending.

It would reorder the events as well, but since it’s vertically it doesn’t change the song.

Plugin = sort by plugin name, alphabetically. So all would be lined up together, as groups.
Type = Track type.
Group = Sort by the groups, alphabetically
Auto = Automation. Sort the track list based on existing automation. User would set up the default order. Volume, pan etc. So then all tracks with volume automation would be sorted to the top.
And probably a column for Time. Sorted top to bottom, where the track events exist chronologically. Based on the location of the tracks’ first event. The left most event (chronologically first) would be at the top of the list.

I think that I like this idea.

Ah, you feel personally attacked and now you are biting back. Sorry for that.
A lot of your proposal has at its basis that users always use track colors to distinguish the track type. And that is simply a wrong assumption. As a consequence most of your proposal would not resonate well with users who would lose the ability to use track colors to encode a different kind of information.

Please don’t feel offended. I just think your proposal has an obvious flaw and needs to more thought.

Here you go.
This should go without saying, but for everyone that wants to keep things in the stone age cause something something alienation:

Feature improvement suggestions are never without the obvious notion that if people want to keep their ways then go ahead and keep them. To make new things optional. But I guess that I have to articulate that for you.

You could always keep your current cubase version; no one will force you to upgrade to a newer version. And you are the one being attacked because your workflow is under attack by the proposal of a superior system.

You should google how the mind processes colors and come back to me with a new understanding because you don’t even know what you’re arguing against.

I think the database-style track rack is a great idea. And I want to pursue that suggestion. If you want to just make it personal instead of talk about the daw, then leave me alone. I don’t have time for drama; I’m trying to give a company ideas about the program.