2.24

[thcilnnahoj]

No bug, just a little weirdness: When you delete an event that you've got ready in the embedded editor (whichever type), you normally end up with an "empty" embedded editor. If you delete the whole track the event is on, however, the editor will stay and still reference the no longer existing event (provided there are no phantom copies of it left elsewhere).



This happens to the non-embedded editor also when you delete the event that's currently opened in it, but in this case, I think there's not much else to show other than an empty sequence window...

[MelodyMan]

I think it's a bug but i can't really reproduce it. When you want to pan your sounds in the mixer, some meters don't show the panning; both sides (left and right) show activity, when only one side should. You can still hear the panning being done, but the visuals don't show it.

Mind that this goes for only some tracks, that's why it's so weird. I have two guitar tracks with exactly the same plugins and settings on it and one shows the panning and one doesn't.

[thcilnnahoj]

[MelodyMan]

[LiquidProj3ct]

I noticed, since 2.23 I think, that Podium reacts a little slow. Try this with feew 16th notes in loop, mute and unmute the track while it's playing and you will see that the cursor has to move around 1bar or more until the mute/unmute/modified note take effect.

I downloaded another host to test, same drivers, and I hadn't this problem.

[thcilnnahoj]

A little weirdeness again: If you adjust an audio event's volume handle and while dragging, move the cursor near the edge of the tracks region, it will start scrolling lightning-fast: Example GIF (the same happens if you increase volume on a track further down, of course). The area in the example is very cramped, but this happens to me sometimes when I'm on the mixer page, where the tracks view only gets ~40% of the screen. Of course it should scroll if you try to move an event up or down, but not while dragging handles, I think. Edit2: A similar thing occurs when you're resizing a track near the bottom edge. The grabbed edge of the track doesn't follow the cursor anymore after you hit the scroll area at the bottom: Example GIF.

I've also got a question related to this: What's the point of being able to scroll down far, far below the last track, almost into infinity? Shouldn't it behave more like the navigator, stopping when only the last track is visible anymore? Edit: Oh yeah, after you scrolled down so far you no longer see any tracks, the navigator still falsly displays events on the bottom track as visible.

[LiquidProj3ct]

[Zynewave]