Zynewave's Forum Page

@thcilnnahoj wrote:

Tiny aesthetics thing: If the track name is longer than the mixer strip is wide and it gets cut off, there is always still a little padding space on the left side, but not on the right.

Great. I’m glad to see it’s working as I intended 😉

How else would you want it to look? I’ve tried cutting the text off with the same border on the right side, but it does not look good when the text is abruptly cut in mid-air.

Only improvement I can think of is to truncate the text and append “…” to indicate the text does not fit. But I think there are a lot of things on my todo list that have higher priority.

@thcilnnahoj wrote:

Ahem… Not really a bug, but a little visual inconsistency, maybe:
As opposed to other events, the contents of automation events are not colored with the selection text color. Example: red active selection font color – the curve is colored ever so slightly with the track color (green).

Since the automation overhaul, the automation lines may of course be handled a little differently altogether.
By the way, why is it that pan automation events always display a “ghosted” line at the center position as well as the actual line? :-k

Edit: forgot to mention why this can become a problem!
If you use darker selection colors with bright text like I like to do, the selected event’s curve can become rather hard to see. And the same happens at the other end of the spectrum too, of course.

This is a bit tricky. The reason the color of the curve is not the same as the color of e.g. note events, is that the curve is global for the track, and not each individual curve sequence. The curve is also drawn on areas where there are no curve sequences, so the curve color cannot be based on the selection state of the curve sequence events. I’ve now changed it so that the color is based on the timeline fill/text colors instead of the track header colors. That makes it stand out more. But it’s difficult to prevent that extreme track event colors may make the curve line hard to see.

The thin base line for pan tracks just show where zero is. You’ll see the same line for pitchbend tracks etc. The purpose is to make it clear whether the automation is actually changing the parameter, or if it is neutral.

Thanks. The new beta9 should fix these color issues.

@Malcolm: You can load the “Colors – Default” setup to get the old colors back.

@Malcolm Jacobson wrote:

Hi Frits,

I have sent you a sample project file.

While making this file, I noticed that if I created a new Bus track and loaded an effect the Presets were recognised correctly, but they disappeared as soon as I assigned a source to the Bus Return. Assigning the source seems to be the trigger.

Cheers,

Malcolm.

I’ve tested your project, but I cannot detect problems with lost preset data. I may have misunderstood you: Perhaps you are talking about the preset list in the inspector? That list will always update to show presets for the current track/effect track. If you have an effect track selected, assigning a source will deselect the effect track and select the bottom source track. You need to use the select/check buttons in the inspector rack to select the effect you want to edit with the list panels.

If you truly have problems with lost preset data, then please give me detailed instructions on how to reproduce this.

Beta 7 is uploaded, with some bug-fixes. All that remains for the 2.24 release is bug-fixing of the issues reported in the 2.23 topic. Still a few days required for that. I’ll be back online again on the 26th.

Merry Christmas.

@LiquidProj3ct wrote:

I have another bug, sorry 😳

This is a 100% crash too: Right click on any track header in arrangement view, select Template->Save track As Template and turn on “Copy track timeline event to template”. If the track have any clip, it will crash. You can do it with a track that doesn’t have any vst even.

Fixed. Thanks.