Hi,

From R2R NFO file:

90 MB of PNG file ??

Another instance, was testing kuch audio LG drive and while the plugin is ~20 MB, the skin file is 550 MB ? For comparison, I use to make themes for Windows 7 and 8.1 and entire msstyle file use to take under 1 MB, every single time. Kuch Audio devs need 550 MB to archive their bitmaps ? Unbelievable.

Also, remembering reading in the R2R nfo for RX 10, when it first came out, that some very large binary 180 MB or something clones itself 18 times unnecessarily, that's 2 GB of extra space used for no reason at all. R2R took care of it with their custom installer and it just get extracted and copied in one instance, that's all the program needed. Guys at iZotope deemed users to have 18 unnecessary copies of that binary ??

When it's going to stop ? or is it that it's getting worse ?

Shaking my head in disbelief.

Sorry for the rant, and y'all have good day.

 

Long gone are the days where you only had 4k of ROM to play with, now RAM and disk space is a cheap commodity (and so are a lot of developers) that features come before quality. Screw those 3,000 bugs in the backlog, the new shiny feature is what will sell more copies.

 

dude, respectfully it bloatware
worked in the business for near 40 years. every year the price of memory went and the capacity went up , you would see an increase in bloat and in software. plenty of it was good because you needed to scale up sw, plenty of it was bad because people got too lazy with the efficiency.
it was a trade off between efficiency and the amount of money you wanted to spend to achieve it..

MS was always a classic case of bloat

 

That is not "unbelievable". And it is not even remotely comparable to windows theming.

The plugin has a background, LEDs, 2 different meters, at least 2 different knobs (possibly more, varying in perspective) and a toggle switch. All these elements (with the exception of the background) are stacks and contain a lot of frames, depending on the step resolution. Sometimes the individual frames of the stacks are much larger than the actual element because, for example, shadows, reflections, etc, have to be baked in. In addition, the images must be available in a correspondingly high resolution, because otherwise users whose screen offers more than 1080p pixel density will complain about blurred graphics.

How exactly do you want to implement this other than with pixel graphics or vector coding? And creating vectors is a lot (!) of work to make them look like pixel graphics. Especially when we're talking about three-dimensionality.

Flat design is super efficient, but then users complain that it's not three-dimensional enough for them. You just can't please anyone.

 

Last edited: Mar 18, 2024

only 90 meg? that's about a mute button's worth of bitmap graphic files for an Arturia. Some of these "performance improvement" details are a little bit of marketing. In the greater scheme of things, 90mb is nothing.

 

arturia is the king I think ...they have 96 keys of keyboard, all with 16 positions when you press so you get great visual feedback