Do you even know what "vector graphics" means?
It means a list of instructions sent to a graphics package to render bitmaps.
So it means: bitmaps that you need to render first.
Only it requires a graphics rendering library in order to render those bitmaps which is huge and expensive. It also requires a ton of processing power.
For example the existing knobs are "vector graphics", they're 3d models with lighting and shading properties in the 3d renderer "blender". I could incorporate blender if it's possible to utilize it via GPL through external tools and call into those tools via my own code to render the bitmaps. The knobs take about five minutes to render on highest quality at high resolutions like 200x200.
The knobs in the last screenshots are "vector graphics": my own code already includes a rendering library and can draw them in "real-time", which is actually at about 5 fps depending upon your processor. Older versions of the effects (2007-2009) used these knobs and did
render in real-time: in other words they were 100% scalable and vector based.
(Do you remember this vector version of the Xhip GUI? http://xhip.net/temp/xhip.17.5b.zip
In 2011 I decided to buffer them into bitmaps because blitting a bitmap is about 1000x faster. As the number of knobs on the screen increased (or their resolution) the frame rate dropped to 1 fps, 1/10th fps and worse. By pre-rendering the bitmap strips the frame rate is always 1/60 or more until resolutions get into the 100x100 range (default size = 33x33.) This is because even the bitmap blit is 100% software and doesn't use hardware acceleration.
Do you want to write the code? You are very welcome to.
Create a free BSD-licensed GUI library which includes a "vector" rendering library and all the associated components and I'll provide you the interface Xhip uses for its GUI so you can incorporate your GUI into the plug-ins. (You probably don't remember but this is originally how it worked. There were several 3rd party Xhip skins that were never updated. The GUI was an external dll linked in via a defined/stable interface.)
The real issue is these are total shit effects/synths and you people bitch and bitch endlessly about the GUI! The GUI is already 90% of the work (which is why I never included GUIs to start) and you're successfully making it 99.999% of the work.
The tiny 0.001% left over means absolutely no work
gets done on the plug-in itself.
You people (GUI/aesthetics) are incredibly stupid. To be honest I have no idea why I've ever listened to you and have wasted so much of my time. You should really just do the work yourself and shut the f**k up for once.
I honestly should release the next version without GUIs and never release the GUI code again.
You do realize there are about ten other synthesizers and 30+ effects that would exist if it wasn't for you. If these vector based GUIs I wrote ten years ago
were good enough for you.
You do not have the required permissions to view the files attached to this post.