.@LiquidProj3ct wrote:
This is the little piano roll bug I said before:
Best regards 🙂
edit: I’m also getting tons of freezes exiting podium, when the system ask if I want to save the project and I say ‘no’, around 1 each 3 times. I don’t know how to replicate.
To my knowledge Podium has always done that. I thought it was something to do with the scale or zoom of that editor?
@thcilnnahoj wrote:
@thcilnnahoj wrote:
– Track headers don’t always show the same elements even if they’re supposedly the same height after using the ‘set default track height’ option.
It seems this happens because there’s a larger space between selector buttons and the faders when there’s an effect added to the chain.
Here are two tracks – only the second one has effects on it.
On the top row, they’re both at the smallest possible size where you can still see everything except the effect chain. On the bottom row, the additional space is easily visible after setting track size so that you get to see the controls on the second track too.
Thanks. Fixed in the new beta14.
There’s also a little extra space on the right side of the track headers, even when you disable vertical meters and the color bar. It’s more apparent now with the selection frame – it looks a bit strange that it doesn’t cover the whole header.
You mean the space for the horizontal drag bar? Clicking this will not select the track, so I think it would be wrong to extend the focus frame onto this bar.
@LiquidProj3ct wrote:
This is the little piano roll bug I said before:
Best regards 🙂
edit: I’m also getting tons of freezes exiting podium, when the system ask if I want to save the project and I say ‘no’, around 1 each 3 times. I don’t know how to replicate.
That’s intended. Podium will scan how many octaves contains notes in the the displayed range of the sequence event, and then display this centered. In your sequence the second note is placed in the octave below the first note, so the display is offset with an octave.
Please let me know if you find a way to reproduce the freeze bug.
@thcilnnahoj wrote:
@Zynewave wrote:
Sure. Probably coming in 2.24.
Otherwise known as Podium 4.0! =P~
@Zynewave wrote:
– I think the ‘default track color’ setting is ready to be retired. With the default opacity settings, it messes everything up if you select anything but shades of grey.
Can you clarify?
Um, I’ll try, but I can’t guarantee that my explanation will make sense to you! 😆
For reference, example 1 has 2.23’s default color settings: overall color opacity 100%, track background opacity 20%, some random track colors and no default track color assigned.Before 2.23, you could select a default color and still override it when you set per-track colors, provided you set opacity to 100%.
Now, the strips are always colored, even if you set rack/header/strip opacity to 0. Even on higher opacity levels you don’t override the default track color but can only add various track colors to it instead. So you have a choice between all track backgrounds being pretty much shades of the same color (ex. 2, low opacity) or getting a real color mix (ex. 3, high opacity), like in previous versions, but coloring the whole strip this time. All in all very bright compared to the default settings. (Edit: It can of course be dark as well – I meant to say it’s quite intense.)
Setting the default color to a shade of grey is a little more useful, as you can make tracks appear generally brighter or darker, if moderately applied. (Edit: Sorry, this is of course not correct. It can be achieved by setting a lighter or darker shade of the panel background color! It’s just that I always use grey…) 😉
Thanks for the screenshots. You’re right. I made an experiment in beta11, where the opacity setting would fade into the default track color, instead of the panel color. That resulted in the fully colored track background in your screenshot. I’ve now reverted back to fading into the panel color. That makes the “default track color” still relevant, I think 😉
Btw. I’ve modified the default track coloring slightly in the new beta14, and specified a new default track color. Let me know if the new default colors present problems.
@Zynewave wrote:
Btw. I’ve modified the default track coloring slightly in the new beta14, and specified a new default track color. Let me know if the new default colors present problems.
I only did a quick test – is it correct that default track color is not applied to colorless tracks anymore when you save a project? That’s the reason I never used it in the first place, as it quickly became a mess, but it looks like it has been fixed already somewhere along the way…?
There’s also a little extra space on the right side of the track headers, even when you disable vertical meters and the color bar. It’s more apparent now with the selection frame – it looks a bit strange that it doesn’t cover the whole header.
You mean the space for the horizontal drag bar? Clicking this will not select the track, so I think it would be wrong to extend the focus frame onto this bar.
Ah! Since it so distinctly looks like part of the track I assumed it was separate from the drag-handle. You’re right I never tried to select a track there.
If 2.23 is finished, it’d be great if you could take a look at the real-time bounce issue mentioned here: http://www.zynewave.com/forum/viewtopic.php?p=15899#15899. With beta 12 and the new signal chain layout it seems Ctrl-H is gone, and so it’s become impossible to unhide effect tracks so you can insert an empty event to record in manually.
I have a link to that post, and I’ll get back to that eventually. Probably not going to make it into 2.23. As a consequence, in beta14 I have put the “Hide track lane” option back into the selector menus. Eventually I’ll remove the hide track lane option entirely, but only once I get the realtime bounce mended, and fixed some issues with track copy/paste.
Understood! This is also good since I (and I presume others too) still have a handful of old projects that have lots of unhidden tracks. Now they can at least still be “converted.”
From what I can tell, these are the problems I’ve found that made it as far as beta 14:
– Slider value pop-ups become stuck when changing profiles or closing the inspector with shortcut keys.
– The bypass buttons on the selectors do not update to a newly selected mute color until the UI is refreshed.
– If you open the mixer and then select a track in the arrangement view, the mixer strip uses the active selection font color instead of the inactive one.
– Sometimes, the group expand/collapse button will ignore the track color and be colored with the panel background color instead.
– When you’re dragging a device to a track, the selector button’s pop-up help gets a little in the way as it blocks the view of the chain.
– When you drag-and-drop an instrument to a track in a particular way, the “drop here” box overlay on the track becomes stuck. You can even ride it up and down using the scroll-wheel. Yee-ha! 😆
Here’s a GIF animation:
