pavouk100's Forum Page

@Zynewave wrote:

Confirmed. It can happen if you have enabled the “follow play cursor” option in the view menu. I’ll fix this.

Great, I’ve been bitten by this one too. I have also one FR regarding ‘Follow play cursor’ option. It would be nice if view would not scroll in case that the end of the arrangement/loop(if activated) is already present on the screen, but on the very right end. Most prominent example is doubleclicking navigator (ie. zoom exactly to the whole arrangement) and let the whole arrangement play. The view scrolls when play cursor reaches cca 3/4 of the arrangement length, although scrolling in this case is actually distracting and counterproductive.

@LiquidProj3ct wrote:

@pavouk100 wrote:

Ah, ok. But then, how can internal VST ui editor know about correct units?

Because those aren’t VST, they’re ‘z’ plugins 😉

No, I mean really VST plugins , but using podium’s native UI – you can force podium to bypass plugin’s UI (by ‘Use generic editor instead of plugin editor’ checkbox in ‘Device mapping properties’ of any VST plugin). In this case, podium knows very well about proper ranges and units for every tweakable (automatable) parameter, so this leads me to believe that my original requested feature is feasible. 😉

Simple, powerful, awesome. Thank you Fritz, it is real improvement.

I understand that you have a lot of work finishing and polishing this change, but I’d like to suggest two following improvements for automation:

1. When automating VST parameter, would it be possible to see units of the current VST parameter (as e.g. in Podium’s generic VST effect ui), instead of number between 0 to 1?

2. When automating Level, would it be possible to have values from -Inf to +12dB (as mixer faders have) instead of -Inf..0 (in other words, allow also amplification, not only attenuation).

Thanks,
Pavel

@Zynewave wrote:

Creating a new plugin parameter track from the inspector parameter panel or the track context menu, will also create a curve sequence on the track. The current plugin parameter value is set as the starting point in the curve sequence.

Awesome. Thanks a lot, I was always missing this little feature.

@Pigini wrote:

whatelse could be done with layers?
– layer clips could be “transparent” (adding to the events underneath) or “opaque” (replacing events underneath it).
– “clipped” draggable edges, so the sequence within it could be bigger, the clip range working like a selection window. (it might only show a part of whats on the layer)
– could be merged

But IMHO all this can be achieved by putting separate events into child tracks of the track with VSTi, everything needed is already present. Sorry for being in that ‘do not add overlapping or duplicate features’ crowd again 😉

IMHO most of the people believe that cost of the feature is the cost of adding it into the product. But usually, the major cost of the feature is maintaining it – including making sure that it plays nice with other features; it is very common to create ‘snowball’-type of SW, where there is so many ad-hoc added complex features that noone really knows well, only a few users can use them and more importantly, they usually have some unexpected interactions with other ‘features’.

IMO, the main Podium strength is how cute, contained, small, well-thought-out it is. Frits does great job keeping all new added features minimal, cute and unobtrusive – there is not many things you need to learn to be able do all you need. This is because there is rather small amount of basic ‘features’ – basic building blocks, but they can be combined together very nicely, and interact in the way as you expect. This is usually not the case of big SW bloated with thousands of specialized complex functions.

Anyway, I’m too off-topic now. Let’s see how will Frits handle Mike’s suggestion – maybe he will be able to come up with some brilliant idea how to implement it and not complicate life for those who will not need it 😉