Reply To: Preview 2.24: Embedded plugin editors in the rack

Well, it’s your call whether you want to keep the fader frame! 😀
I wouldn’t have a problem with it, apart from that it can potentially clash with the dB markings and I don’t think it’s really needed to find out about the fader’s hitbox size (besides, it looks like the last few pixels on each side of the frame are not inside the fader hitbox area).

@Zynewave wrote:

@thcilnnahoj wrote:

– It seems the “live” color selection on the color picker constantly writes to the hard disk (podium.ini?) – I can even hear it scratching away! 😯
Maybe the color selections could stay in memory and could only be written to file when you leave the UI color selection, by switching back to track color selection.

That must be because you have a track background image in the project properties? The original image is reloaded to apply the panel dye coloring. To avoid this Podium would need to keep two copies of the image in memory, which I think is a waste.

Forget about it… It’s a known problem with the graphics card I had to put in yesterday because the old one died (that’s the third one for ATi for me). Nothing to do with hard disks! 🙂
What remains is that using the color picker for this purpose produces massive CPU use.
I didn’t use a background image before, but I gave it a try just now. It updates images dyed with the timeline fill color with a little delay – since you said it has to reload the image, that’s probably depending on the image dimensions or file size, right?

I’ve got a suggestion for the mixer zoom slider: Since it zooms in little steps, like the other zoom sliders too, it’d be nice to be able to use it with the scroll-wheel in the same way.